Confirm, emeritus
1,737
edits
Changes
m
I suspect most (if not all) localizers If you already have an SVN accounts for account from another project (like mozilla.com (from [https:) you should reopen the original bug and ask for additional write permissions to /addons/trunk/site/app/bugzilla.mozilla.orglocale/show_bug___ where ___ is your locale.cgi?id=356627 bug 356627]). If you don't have an SVN account alreadyyet, and you would like to be able to manage the files in SVN yourself (this is everything that isn't dynamic data), please:* Reopen the original bug that was filed to get you mozilla.com SVN access* In the comments, request SVN access to (replace ___ with your locale):** svn+sshfollow [http://svnwiki.mozilla.org/addons/trunk/site/app/locale/___SVN#SVN_account_for_localizers these instructions].
→Steps to localizing AMO in a new language
After a locale has been setup, it's possible for a localizer to add/edit translations with little to no help from the admins/developers. We're happy to assist if we can, but once a localizer learns the process, we usually just slow things down, so:
I'd also recommend subscribing to the rss feed for your locale. You can get to the feeds from [http://viewvc.svn.mozilla.org/vc/addons/trunk/site/app/locale/ viewvc]. When a new string is added, the developers will merge the string into your file and mark it as fuzzy. If you're subscribed to the feed, you'll be notified of the change almost immediately.
= What about the extension metadata? =
AMO supports localized metadata about the extensions (like their titles and descriptions) but offers no way for localizers to directly edit them. The responsibility for translation lies solely with the authors. We're looking at more usable ways to implement the system and still keep a good level of quality and accuracy. In the mean time, add-on authors are given this brief [http://developer.mozilla.org/en/docs/Localizing_extension_metadata_on_addons.mozilla.org summary on how to get help].
