AMO:Localizers: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
mNo edit summary
 
(9 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{amo|localizers=selected}}
[https://wiki.mozilla.org/AMO:Localizers#What_is_localservice1_in_the_.po_files Wondering what localservice1 is in your .po file?]


= Introduction =
= Introduction =
One of the big advantages of Remora is support for localization.   
Hi, thanks for your interest in localizing addons.mozilla.orgThe site is available in so many languages because of people who volunteer their time to make everyone's experience better.  An overview of L10n status can be found at https://addons.mozilla.org/localizers.
 
Generally, localizations will only be accepted from people who are already active members of a [http://wiki.mozilla.org/Category:L10n_Teams language team] which starts [http://developer.mozilla.org/en/docs/Localization here].


= Steps to localizing AMO in a new language =
= Steps to localizing AMO in a new language =
Line 10: Line 8:
This is a comprehensive list of steps to completely localize addons.mozilla.org's interface from English into another language.
This is a comprehensive list of steps to completely localize addons.mozilla.org's interface from English into another language.


* If you don't already have one, create a new [https://addons.mozilla.org/en-US/firefox/users/register AMO Account]
* You'll need to be an active member of an existing [http://wiki.mozilla.org/Category:L10n_Teams language team] or have approval from one of their leaders.  If your language's team doesn't exist yet, [http://developer.mozilla.org/en/docs/Localization start here].
 
* If you don't already have one, create a new [https://addons.mozilla.org/firefox/users/register AMO Account] (Note that this will soon be replaced with BrowserID.  This is a wiki, feel free to change when that happens. :)


* [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=addons.mozilla.org&component=Localization Search Bugzilla] for the words "AMO Localization (xx)" where xx is your locale code.
* [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=addons.mozilla.org&component=Localization Search Bugzilla] for the words "AMO Localization (xx)" where xx is your locale code.
Line 19: Line 19:
* Join the [https://lists.mozilla.org/listinfo/dev-l10n-web dev-l10n-web mailing list] so you can get notified when strings are added or changed
* Join the [https://lists.mozilla.org/listinfo/dev-l10n-web dev-l10n-web mailing list] so you can get notified when strings are added or changed


* Translate the main [http://svn.mozilla.org/addons/trunk/site/app/locale/en_US/LC_MESSAGES/messages.po english gettext file]
* Strings can be edited either directly via SVN or via [https://localize.mozilla.org/ Verbatim, an online tool]
** If you already have an SVN account from another project (like mozilla.com) you should reopen the original bug and ask for additional write permissions to /addons/trunk/site/app/locale/___ where ___ is your locale.
** If you don't have an SVN account yet, follow [http://wiki.mozilla.org/SVN#SVN_account_for_localizers these instructions]
 
* Since you've got a bug filed, someone from the AMO team will initialize your language for you in the SVN repository and you'll have two blank .po files - one messages.po and one javascript.po.  They are both in the same directory.  As an example, the English messages.po file is here (your's will use your locale code): http://svn.mozilla.org/addons/trunk/site/app/locale/en_US/LC_MESSAGES/messages.po
** If you're not sure what the Plural-Forms are for your language, mention this in the bug and we can help
** If you're not sure what the Plural-Forms are for your language, mention this in the bug and we can help
** Attach the completed document to your bug


* Translate the [http://svn.mozilla.org/addons/trunk/site/app/locale/en_US/pages/ specialized pages] ''except for privacy.thtml''
* Once the language is initialized your bug will be closed and you'll be able to commit changes to your locale's .po file. When you reach 100% translated reopen the bug and the AMO team will enable the locale on the production site.
** [https://bugzilla.mozilla.org/show_bug.cgi?id=372995 We can't accept translations of privacy.thtml at this time]
** Attach each of the translated files separately to your bug


* Translate [http://wiki.mozilla.org/Update:Remora_Sandbox_Flowchart the strings for the flowchart]
* You can view your string changes on the site a few minutes afer you commit on https://addons-dev.allizom.org/
** We'll create the image for you, just attach the translated strings to your bug


* When this is all complete, please post a comment in your bug asking for all updates to be pushed to the staging site for review.
= What is localservice1 in the .po files =
AMO ships with a default set of social media links that people can use to share add-ons (for example, Twitter, Facebook, etc.).  We chose the most appropriate social media links for English speakers but realize that those aren't always the most used in other locales.  If you would like to add your own services to the sharing options  you can use these.  The .po file looks like this:


* Once everything is setup, when you login to addons.mozilla.org, there will be a link in the left menu that says "localizer tools.It holds links to change dynamic data in the system - it's pretty intuitive, but if you'd like more instruction here, look us up in #addons on irc. ''You should look at this link as soon as it's available to you on the live site, because all the categories, add-on types, etc. are here and need to be translated.''
msgid "localservice1"
msgstr ""
msgid "Post to localservice1"
msgstr ""
   
msgid "http://localservice2/?url={url}&title={title}"
  msgstr ""


'''An optional (but recommended) aside:'''
You should adjust the .po file to replace localservice1 in the ''msgstr''s to be the name of your service.  For example, if I wanted to share on Hatena::Bookmark I would adjust the .po file like this (Note that the first msgid, the one with only the name of the service, should remain in ascii characters):


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:
msgid "localservice1"
msgstr "hatenabookmark"
msgid "Post to localservice1"
msgstr "はてなブックマークへ投稿"
msgid "http://localservice1/?url={url}&title={title}"
  msgstr "http://b.hatena.ne.jp/append?{url}"


I suspect most (if not all) localizers already have SVN accounts for mozilla.com (from [https://bugzilla.mozilla.org/show_bug.cgi?id=356627 bug 356627]).  If you have an account already, and you would like to be able to manage the files in SVN yourself (this is everything that isn't dynamic data), please:
This is a somewhat unique and potentially confusing way to add sharing services (but is also the most convenient for localizers) so feel free to ask the dev-l10n-web mailing list if you have questions.
* 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+ssh://svn.mozilla.org/addons/trunk/site/app/locale/___


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.
'''If you don't want to use local sharing services leave these strings blank'''


= How about the pages behind authentication? =
AMO maintains an experiemental version of the site at https://landfill.addons.allizom.org/ which localizers are welcome to have administrative privileges on and can therefore see any part of the site.  [http://micropipes.com/blog/2011/03/29/welcome-to-the-landfill/ Learn more]


= What about the extension metadata? =
= 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].
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].

Latest revision as of 00:45, 10 July 2012

Wondering what localservice1 is in your .po file?

Introduction

Hi, thanks for your interest in localizing addons.mozilla.org. The site is available in so many languages because of people who volunteer their time to make everyone's experience better. An overview of L10n status can be found at https://addons.mozilla.org/localizers.

Steps to localizing AMO in a new language

This is a comprehensive list of steps to completely localize addons.mozilla.org's interface from English into another language.

  • You'll need to be an active member of an existing language team or have approval from one of their leaders. If your language's team doesn't exist yet, start here.
  • If you don't already have one, create a new AMO Account (Note that this will soon be replaced with BrowserID. This is a wiki, feel free to change when that happens. :)
  • Search Bugzilla for the words "AMO Localization (xx)" where xx is your locale code.
    • If a bug appears for your locale, then someone is already working on it. This will be a case by case basis depending on how far along the translation is, but if the bug isn't resolved, I'd suggest commenting in the bug and offering to help there.
  • Assuming a bug doesn't exist, create a new bug with a Summary of "AMO Localization (xx)" (replace xx with your locale) and a description announcing your intention to localize AMO for that locale (include your AMO account name, please!). Assign the bug to yourself.
  • Strings can be edited either directly via SVN or via Verbatim, an online tool
    • If you already have an SVN account from another project (like mozilla.com) you should reopen the original bug and ask for additional write permissions to /addons/trunk/site/app/locale/___ where ___ is your locale.
    • If you don't have an SVN account yet, follow these instructions
  • Since you've got a bug filed, someone from the AMO team will initialize your language for you in the SVN repository and you'll have two blank .po files - one messages.po and one javascript.po. They are both in the same directory. As an example, the English messages.po file is here (your's will use your locale code): http://svn.mozilla.org/addons/trunk/site/app/locale/en_US/LC_MESSAGES/messages.po
    • If you're not sure what the Plural-Forms are for your language, mention this in the bug and we can help
  • Once the language is initialized your bug will be closed and you'll be able to commit changes to your locale's .po file. When you reach 100% translated reopen the bug and the AMO team will enable the locale on the production site.

What is localservice1 in the .po files

AMO ships with a default set of social media links that people can use to share add-ons (for example, Twitter, Facebook, etc.). We chose the most appropriate social media links for English speakers but realize that those aren't always the most used in other locales. If you would like to add your own services to the sharing options you can use these. The .po file looks like this:

msgid "localservice1"
msgstr ""

msgid "Post to localservice1"
msgstr ""

msgid "http://localservice2/?url={url}&title={title}"
msgstr ""

You should adjust the .po file to replace localservice1 in the msgstrs to be the name of your service. For example, if I wanted to share on Hatena::Bookmark I would adjust the .po file like this (Note that the first msgid, the one with only the name of the service, should remain in ascii characters):

msgid "localservice1"
msgstr "hatenabookmark"

msgid "Post to localservice1"
msgstr "はてなブックマークへ投稿"

msgid "http://localservice1/?url={url}&title={title}"
msgstr "http://b.hatena.ne.jp/append?{url}"

This is a somewhat unique and potentially confusing way to add sharing services (but is also the most convenient for localizers) so feel free to ask the dev-l10n-web mailing list if you have questions.

If you don't want to use local sharing services leave these strings blank

How about the pages behind authentication?

AMO maintains an experiemental version of the site at https://landfill.addons.allizom.org/ which localizers are welcome to have administrative privileges on and can therefore see any part of the site. Learn more

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 summary on how to get help.