On Tue, May 26, 2009 at 05:51:23PM +0200, F Wolff wrote:
> > #. Input Method: English mode
> > #: ../im.c:75
> > msgid "English"
> > msgstr "Engels"
> Since there is nothing really "English" about the Latin input method,
> can we translate it with the local language name, in other words
> "Afrikaans" in this case?
Really, no reason to translate it at all, unless your locale has
IM support, in which case, yes, "Latin" or "Afrikaans" would make sense.
> > #. Input Method: Traditional Chinese mode
> > #: ../im.c:90
> > msgid "ZH_TW"
> > msgstr "ZH_TW"
> Is this the string shown to the users? Isn't it better to call it
> "Traditional Chinese", or something like that?
Hrm, yeah good point. The only locale where it even makes sense to
translate that string is zh_TW -- again because the fact that it only
appears during IM usage.
(So, in fact, noone ever sees "ZH_TW". People using Tux Paint with
the Traditional Chinese locale will see the trad. Chinese name for
trad. Chinese. :) )
What's a good way to denote these, both in terms of msgid and in terms
of what text we bother translating?
Should these strings simply not be gettext()'d at all?
(e.g., in the Chinese Input Method source code, replace
'gettext("ZH_TW")' and 'gettext("English")' with the actual trad. Chinese
(Though, how reasonable is it to have Chinese glyphs inside a C string in
a .c file?)