On 06.04.2008, at 04:22, Korakurider wrote:
Hi, Original NaturalLanguaeTranslator implementation has sort of fallback functionality: If translation isn't found for current locale, try again for parent locale (see #translate: ).
Makes sense.
I omitted it from gettext translator but adding it would be trivial. How we want to handle the setting would be more difficult part (how to tweak LocaleID>>current,
We could extend the LocalePlugin to return a list of language codes, or as a cheap solution pass LANGUAGE on the command line (is it really LANGUAGE not LANG?).
to store in project? etc)
Not sure what you mean here.
I think this fallback thing would be useful for some situation, but we also need to make etoys translation easier. Translators community have been asking for this.
Certainly, though I do not see how supporting fallback languages would negatively affect translators.
- Bert -
Cheers /Korakurider
On Sun, Apr 6, 2008 at 1:47 AM, Bert Freudenberg bert@freudenbergs.de wrote:
Takashi, Korakurider,
do we support this in Etoys? If not, what would need to be done to allow it?
- Bert -
Begin forwarded message:
From: Khaled Hosny khaledhosny@eglug.org Date: 5. April 2008 12:05:20 MESZ To: Bert Freudenberg bert@freudenbergs.de Cc: Localization mailing list localization@lists.laptop.org Subject: Re: [Localization] code comments?
Yes, by setting LANGUAGE env variable with a fall back language, some thing like "LANGUAGE=ur_PK:fa_IR:ar", you can specify multiple fall back languages.
On Sat, Apr 05, 2008 at 09:31:30AM +0200, Bert Freudenberg wrote:
... which reminds me: Is it possible in gettext to fall back on a language other than English when a translation for some phrase cannot be found? That would be a useful feature I think, as long as there are programs that are not fully translated (which will happen very often).
- Bert -