Use extension's existing translations for the AMO name and summary?

Add-ons addons.mozilla.org
#1

It’s possible to include translations for an extension’s name and description in _locales/{lang}/messages.json files. These display when someone installs the extension, but don’t seem to be used for the extension’s page on addons.mozilla.org. Instead, we have to go through each language one by one and copy and paste these strings into the name and summary fields.

Am I missing something obvious, or is this the only way to update the name and summary?

#2

I’d love to have an API that lets you update the listing info translations, so you can use a translation tool and easily import the strings to AMO.

1 Like
#3

Are you looking for something like following found on https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Internationalization ? :

Retrieving localized strings in manifests

Your manifest.json includes strings that are displayed to the user, such as the extension’s name and description. If you internationalize these strings and put the appropriate translations of them in messages.json, then the correct translation of the string will be displayed to the user, based on the current locale, like so.

To internationalize strings, specify them like this:

"name": "__MSG_extensionName__",
"description": "__MSG_extensionDescription__",

Here, we are retrieving message strings dependant on the browser’s locale, rather than just including static strings.

To call a message string like this, you need to specify it like this:

  1. Two underscores, followed by
  2. The string “MSG”, followed by
  3. One underscore, followed by
  4. The name of the message you want to call as defined in messages.json , followed by
  5. Two underscores
__MSG_ + messageName + __
#4

@stig thanks for this, but yeah I’m already doing that. The translations are displaying correctly in multiple languages in about:addons, but not in the public page on addons.mozilla.org.

I had thought that the latter would display the strings from the _locales files if there wasn’t anything else specified, but it seems that it doesn’t.

1 Like
#5

It displays the strings specified in the amo management ui for the extension listing. These strings by default will use the ones from the extension when creating the listig, but they aren’t kept in sync afterward.

1 Like
#6

Hi guys, sorry to long insistence, but how to install the translate add-on on Firefox Android, because addons.mozilla.org isnt possible.