Localization of AMO and some other pages of Mozilla.com
Cédric Corazza
About the AMO localization:
I've read that AMO should be localized and I haven't seen anything new
about it yet. I'm aware that all of the locales can't handle the
translation of all the extensions and themes : 1800 add-ons is huge for
our community (and even for a proprietary editor). But at least, giving
the opportunity for locales to translate the most popular/downloaded
ones would be a good compromise (I meant shared menus, buttons and short
description). This wouldn't be mandatory, if an addon page is not
translated, then it will fall back to en-US page which is the current
state. As odd how it sounds, most of my fellow citizen (and I guess it
is the same for other locales) are repelled by English :-D .
About the remaining Web pages accessible through the UI and that are not
localizable:
It would be also good that those pages (release notes, anti-phishing
stuff and so) could be localized (but not mandatorily: fallback on en-US
page).
Regards
Axel Hecht
> Hi,
> About the AMO localization:
> I've read that AMO should be localized and I haven't seen anything new
> about it yet. I'm aware that all of the locales can't handle the
> translation of all the extensions and themes : 1800 add-ons is huge for
> our community (and even for a proprietary editor). But at least, giving
> the opportunity for locales to translate the most popular/downloaded
> ones would be a good compromise (I meant shared menus, buttons and short
> description). This wouldn't be mandatory, if an addon page is not
> translated, then it will fall back to en-US page which is the current
> state. As odd how it sounds, most of my fellow citizen (and I guess it
> is the same for other locales) are repelled by English :-D .
Those are a bunch of items. AMO l10n will come with remora, that is, the
localization of that webapp. The localization of extension descriptions
on the other hand is a different bug,
https://bugzilla.mozilla.org/show_bug.cgi?id=257155, which is not fixed
for 2.0, and there is hardly anything that the webapp can do about that,
AFAICT. As long as it pulls the extension data from install.rdf, at least.
I'm not exactly sure what you mean by "shared menus, buttons and short
description", though.
> About the remaining Web pages accessible through the UI and that are not
> localizable:
> It would be also good that those pages (release notes, anti-phishing
> stuff and so) could be localized (but not mandatorily: fallback on en-US
> page).
Sounds like this should have a better chance in .l10n.web. AMO questions
may be better off in .extensions, even, but I haven't found any active
discussions on remora in google groups, so I'm not cross posting there.
Cross-posting and setting follow up.
Axel