"Stephen J. Turnbull" wrote:
>>>>> "Hrvoje" == Hrvoje Niksic
<hniksic(a)iskon.hr> writes:
Hrvoje> Giacomo Boffi <giacomo.boffi(a)polimi.it> writes:
>> ============== SHEER UGLINESS ==============
Hrvoje> Well, I think they're real purdy. :-)
You obviously haven't tried this with a localized menubar. Until
somebody translates (and accelerates) the menubar, you're going to
have this kind of mottled effect with randomly scattered underlines.
Has anybody thought about how to make accelerators "purdy" in Japanese
and Chinese? On second thought, how they are supposed to work at all?
For the implementor's information, Japanese accelerators under Windows
are indicated by an underlined Roman capital letter, following the
English Windows usage and making no attempt to correlate with the
Japanese pronunciation, in parens following the Japanese menu item.
This is going to be very space-intensive on the menubar. And it would
be nice if we had a function to ensure cross-language consistency.
(Or maybe not; do Spaniards who've caught a Windose see accelerators
matching the Español, or imports from the Inglés, on screen?)
Would it be possible to have accelerators that only show up when the
Menu key (whatever it is) is pressed?
Is there a face for accelerators, or is the underline thing hardwired?
Oh yeah, the accelerators for _M_ule and C_m_ds are the same. This
kind of collision is going to be hard to avoid with the relatively
dynamic XEmacs menubar.
I put Mule underneath Edit. I can't yet compile with Mule support, and it
looks like I forgot to fix mule-cmds.el. BTW, I have proposed (in Arch.
XEmacs) to add support for menu item tags, so you can rearrange things more
easily.
By the way, Ben's improvements have made a bunch of work for menubar
localizers (who already have localized menus to work with---obviously
it doesn't matter for those who will be starting fresh). Not to
mention making finding menu items whose translations haven't changed a
process of trial and error for those non-English speakers who do have
localized menubars. There really should be some way for those who
want to keep an old organization to do so, rather than having this
kind of wholesale change enforced on them (at a potentially severe
cost in usability).
This is not feasible. Should XEmacs keep old copies of itself stored in its
code, so you can undo back to arbitrary levels of UI change?
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
_________________ _________________ _________________ _________________
What are those straight lines for? "XEmacs rules."
--
Ben
In order to save my hands, I am cutting back on my mail. I also write
as succinctly as possible -- please don't be offended. If you send me
mail, you _will_ get a response, but please be patient, especially for
XEmacs-related mail. If you need an immediate response and it is not
apparent in your message, please say so. Thanks for your understanding.
See also
http://www.666.com/ben/typing.html.