Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
SeaMonkey Bug 789724 - Rename "Other Languages" to "Unicode" on the Fonts pref pane (port TB bug 323747)
20 views
Skip to first unread message
Philip Chee
Sep 21, 2012, 5:51:33 AM9/21/12
to
So we are planning to change the en-US string from "Other Languages" to
"Unicode". Normally we would change the entity name to force all locales
to retranslate this string. However we notice that some locales are
already using "Unicode" (or something equivalent) so this would create
unnecessary churn for those translators.
Alternately we could not change the entity name but send a heads up to
this newsgroup and leave it up to the various translation teams to
decide on whether they needed to change their translations or not.
Opinions?
Phil
SeaMonkey Wrangler
--
Philip Chee <phi...@aleytys.pc.my>, <phili...@gmail.com>
http://flashblock.mozdev.org/ http://xsidebar.mozdev.org
Guard us from the she-wolf and the wolf, and guard us from the thief,
oh Night, and so be good for us to pass.
"Unicode". Normally we would change the entity name to force all locales
to retranslate this string. However we notice that some locales are
already using "Unicode" (or something equivalent) so this would create
unnecessary churn for those translators.
Alternately we could not change the entity name but send a heads up to
this newsgroup and leave it up to the various translation teams to
decide on whether they needed to change their translations or not.
Opinions?
Phil
SeaMonkey Wrangler
--
Philip Chee <phi...@aleytys.pc.my>, <phili...@gmail.com>
http://flashblock.mozdev.org/ http://xsidebar.mozdev.org
Guard us from the she-wolf and the wolf, and guard us from the thief,
oh Night, and so be good for us to pass.
Eduardo Trápani
Sep 21, 2012, 10:42:12 AM9/21/12
to dev-l10n
> to retranslate this string. However we notice that some locales are
> already using "Unicode" (or something equivalent) so this would create
> unnecessary churn for those translators.
>
> Alternately we could not change the entity name but send a heads up to
> this newsgroup and leave it up to the various translation teams to
> decide on whether they needed to change their translations or not.
>
> Opinions?
Based on the current translations[1] I suggest to change the entity name
> already using "Unicode" (or something equivalent) so this would create
> unnecessary churn for those translators.
>
> Alternately we could not change the entity name but send a heads up to
> this newsgroup and leave it up to the various translation teams to
> decide on whether they needed to change their translations or not.
>
> Opinions?
so we make sure that nobody misses the modification.
Right now the count for 'release' is:
Total: 103
"Other languages": 88
"Unicode": 15 (ca, el, es-ES, es-MX, gu-IN, hy-AM, it, km, ko, lt, pl,
pt-PT, sk, sl, sq)
I took all the locales without spaces in the translation and checked
them (for example jp and zh do say "other languages"). While not
perfect, I think this should be pretty close to the actual numbers.
Eduardo.
http://mxr.mozilla.org/l10n-mozilla-release/search?string=font.langGroup.unicode&find=browser%2Fpreferences%2Ffonts.dtd&findi=&filter=^[^\0]*%24&hitlimit=&tree=l10n-mozilla-release
0 new messages