[Etoys-notify] [JIRA] Updated: (SQ-129) Some language names appear in English

jira at immuexa.com jira at immuexa.com
Tue Apr 28 13:46:41 EDT 2009

     [ http://tracker.immuexa.com/browse/SQ-129?page=all ]

timothy updated SQ-129:

    Fix Version: M4: production & language (aug)
                     (was: M2: second alpha (june))

> Some language names appear in English
> -------------------------------------
>          Key: SQ-129
>          URL: http://tracker.immuexa.com/browse/SQ-129
>      Project: squeakland
>         Type: Improvement
>   Components: etoys
>     Reporter: team
>     Priority: Eventual
>      Fix For: M4: production & language (aug)

> From TRAC Ticket #8150 (bert, august 2008)
> In the language menu, some languages are listed in their native spelling, and some with their English names. The native name should always be shown.
> (korakurider) I think it would make some sense to show language name in English. Some languages need additional font to show native spelling and thay may cause longer start up time and bigger resource footprint even if the language will not be used in the user session. Or corrupted display if defer font loading.
> Said that,
> Etoys already has code to provide translation for language name via translation dictionary. magic phrase '<language display name>' is the string for this. (see LocaleID>>displayName)
> Problem is now the magic phrase isn't exported to POT. (I can't figure out when #translatedNoop was missed...) If translation isn't provided for the magic phrase, definition in #isoLanguages is used that is English.
> Legacy in-image dictionaries have the string while the translations are mix of English name translated ones.
> We could just add #translatedNoop to the magic phrase and regenerate POT, but that would put the entry in place in PO hard for people to locate. So Yoshiki's aproach of 2101NatLangExtraInfo-yo (see #8163) would be better. But please reuse existing string and don't invent new one!

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

More information about the Etoys-notify mailing list