12:06 p.m.
"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes:
Hrvoje> Well, I think they're real purdy. :-)
You obviously haven't tried this with a localized menubar.
Indeed, I haven't. But accelerators are easy to add to the
translations, aren't they? You just use the same %_ convention.
Has anybody thought about how to make accelerators "purdy"
in
Japanese and Chinese? On second thought, how they are supposed to
work at all?
I certainly haven't. The Japanese and Chinese will have to provide us
with input regarding that issue.
For the implementor's information, Japanese accelerators under
Windows are indicated by an underlined Roman capital letter,
That's sort of like Ben's numbered accelerators provided for menus
that don't have explicit ones.
Oh yeah, the accelerators for _M_ule and C_m_ds are the same.
I've complained about that. The same goes for "_M_essage" with Gnus.
I don't know what's wrong, but I assume Ben will fix it.
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).
Yes. Most improvements make a bunch of work for someone. Translators
should be prepared to deal with a moving target.
2:48 a.m.
New subject: Accelerator I18N [was: I don't wont the f* underlinings ...]
>>>> "Hrvoje" == Hrvoje Niksic
<hniksic(a)iskon.hr> writes:
> 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).
Hrvoje> Yes. Most improvements make a bunch of work for someone.
Hrvoje> Translators should be prepared to deal with a moving
Hrvoje> target.
Definitely not. Translators are volunteers, just like almost all of
our developers. Menus are the translator's API; we should avoid
making work for them just as we avoid making work for programmers
working on other modules. We don't make API changes without
discussion beforehand, we should not make extensive menu changes
(other than adding new functionality) without similar discussion.
Assuming we take I18N halfway seriously. Given the support that ETL
has provided, I should hope we do....
What Ben did moved _all_ of the menu commands I ever use under English
titles, none of whose common Japanese synonyms (at least in my wife's
usage) correspond to the terms used for those menus in Japanese, and
some of which are abbreviations that a typical Japanese could not
parse. Others are outright misleading: "Internet" in Japanese means
IE and Netscape, but no Japanese use them for mail, so they wouldn't
think to look there for mail, and probably not for Gnus.
Unless people messing with the menus plan to be, pay, or otherwise
support, the translators, or say "fuck I18N", they should take the
fact that they are potentially crippling XEmacs for some users into
account, and provide a backwards compatibility option.
-
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."
3:27 a.m.
New subject: Accelerator I18N [was: I don't wont the f* underlinings ...]
hey hey, please cc me if you want to flame me. otherwise i probably won't see
it for quite some time.
"Stephen J. Turnbull" wrote:
>>>>> "Hrvoje" == Hrvoje Niksic
<hniksic(a)iskon.hr> writes:
>> 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).
Hrvoje> Yes. Most improvements make a bunch of work for someone.
Hrvoje> Translators should be prepared to deal with a moving
Hrvoje> target.
Definitely not. Translators are volunteers, just like almost all of
our developers. Menus are the translator's API; we should avoid
making work for them just as we avoid making work for programmers
working on other modules. We don't make API changes without
discussion beforehand, we should not make extensive menu changes
(other than adding new functionality) without similar discussion.
Assuming we take I18N halfway seriously. Given the support that ETL
has provided, I should hope we do....
What Ben did moved _all_ of the menu commands I ever use under English
titles, none of whose common Japanese synonyms (at least in my wife's
usage) correspond to the terms used for those menus in Japanese, and
some of which are abbreviations that a typical Japanese could not
parse. Others are outright misleading: "Internet" in Japanese means
IE and Netscape, but no Japanese use them for mail, so they wouldn't
think to look there for mail, and probably not for Gnus.
Unless people messing with the menus plan to be, pay, or otherwise
support, the translators, or say "fuck I18N", they should take the
fact that they are potentially crippling XEmacs for some users into
account, and provide a backwards compatibility option.
-
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.
9012
days inactive
9013
days old
2 comments
3 participants
participants (3)
-
Ben Wing -
Hrvoje Niksic -
Stephen J. Turnbull