The Add-on Localization Campaign is happening: Join us!

Any additional pair of eyes that could go through the remaining French suggestions and add new suggestions when they see fit would definitely be useful and speed up the review process :slight_smile:
There’s a number of things that native speakers should be able to catch, without any specific localization knowledge and without having the style guide in mind

Cheers!

Campaign day 14 - Stats (last day!)

Quick re-cap of the day: Chinese, Spanish, Italian, Dutch have all suggestions approved. German and French are almost there and Portuguese is also close. Congratulations for the amazing work!

  • Number of participants: 101
  • Words translated: 92657

Progress

Tomorrow we will be packing all locales with 100% completion and generating the add-ons with the localized strings for testing in context, ideally we want to send the strings to authors by the end of the week.

imagen

I’ll be providing a more detailed report in the coming days.

3 Likes

why are we not doing localization in Hindi?

Please check the FAQ in the first message of this topic.

We have generated the add-ons with the localized strings for testing for the 7 locales that have completed all suggestions: Chinese, Spanish, Italian, Dutch, German, French, Portuguese.

We would need to install and test them in these locales to give the green light, ideally before Thursday, so we can send the strings to authors and they upload a new version during the weekend.

How to test the localized add-ons

  1. Get the zip file with all localized add-ons.
  2. Extract the file in any local directory
  3. Open Firefox in your locale
  4. Open about:debugging in a tab
  5. Click on Load Temporary Add-on
  6. Open the manifest.json from the add-ons folder where you extracted the zip
  7. Test the add-on and its metadata in about:addons
  8. If all the strings look good for your locale, please reply to this topic.
  9. If there are some strings with errors, please use the link in the first post pointing to your locale to search the problematic strings, fix them and ping us back to generate a new zip file with the changes.

Edit (July 3, 2018 5:20 PM (UTC)): Zip file updated to include strings fixes during today and pinterest add-on which was missing due an issue with AMO site this morning.
Edit (July 4, 2018 9:30 AM (UTC)): Zip file updated with latest changes.
Edit (July 5, 2018 10:30 AM (UTC)): Zip file updated with latest changes.

1 Like

Thanks for the great work this week testing and reporting issues with the add-ons and correcting the misplaced strings :smiley:

We have just updated the zip file with the string changes you provided in the past days for completed locales: Chinese, Spanish, Italian, Dutch, German, French and Portuguese.

It would be great if we can have green light to send the strings to authors by the end of today or tomorrow so they have time to upload a new version to Addons site and we can start promoting your great work by next Wednesday (July 11th).

Thanks!

Hello everyone,

We are going to proceeded to send the localized strings to developers and we will ask them to have an update published by next week, when we also want to publish a few blog posts and tweets promoting your awesome work.

We are also updating the Addons site summaries and descriptions, some of them are already live :slight_smile:

I keep you updated about the progress next week.

Thanks SO much for your help, have a happy weekend!

Cheers

Quick update, most of the authors have already published a new version of their add-ons with the localized strings.

We are just waiting for the last ones to be able to publish a blog post and tweets promoting the work.

Hi,

thanks for letting New Tab Override be part of this campaign! Just a small feedback: I had a bit extra work because you picked an old version of New Tab Override.

09.06.2018: NTO 13 has been released
15.06.2018: Start of the localization campaign with the strings of NTO 12

Fortunately there were no new strings in NTO 13, only removed strings (so there was a bit unnecessary translation work), two strings combined into one string and an added “.” in one string.

Also I reverted all “\/” to “/” because an unnecessary escape character has been added in all strings with “/”. I know that escaping the forward slash is allowed in JSON but since I don’t do this I reverted this change in all my translations.

No big issues, but maybe this feedback is helpful for the next localization campaign. Again: Thank you very much! <3

2 Likes

We have just published a blog post with a recap here:

https://blog.mozilla.org/addons/2018/07/16/no-longer-lost-in-translation/

Special thanks

I would like to thank some of the people who were part of this campaign:

  • Scott Devanley and Jorge Villalobos - Add-ons team, key members of the project execution.
  • Amy Tsay and Caitlin Neiman - Key stakeholders in the Add-ons team.
  • Ben Miroglio - Leading our metrics approach.
  • Kirby Fowle and Cherry Parks - Marketing team stakeholders.
  • Konstantina Papadea, Lucy Harris and George Roter - Open Innovation input to this project
  • Mozilla’s Localization team - For their key input into the campaign approach.
  • Ton - Dutch core localizer
  • Theo Chevalier - French core localizer
  • Sara and Saverio Morelli - Italian core localizers
  • Xcffl, Shaohua and YFdyh000 - Chinese core localizers
  • Marcelo Ghelman, Cynthia Pereira and Felipe - Portuguese (Brazil) core localizers
  • Philipp - German core localizer
  • Unclenacho, Angela Velo, Pedro Garcia and Jordi Cuevas - Spanish core localizers
  • Mar, Anticisco and Michal Dziewonski - For their support to Japanese, Russian and Polish.
  • The 100 volunteers that contributed to this campaign.
  • Add-on authors for their collaboration.

Our next step is to keep measuring extensions usage in these languages to understand how having them localized influence their installs and usage, we believe that as a result of this campaign more users will install extensions and as a result increase their engagement with Firefox.

We will be reporting back with our finding as soon as we have them.

1 Like

Your awesome work is being mentioned today in diverse big sites and social media:

https://thenextweb.com/apps/2018/07/17/mozilla-wants-to-localize-the-most-popular-firefox-add-ons/

https://www.techradar.com/news/volunteers-translate-the-most-popular-firefox-extensions-into-seven-languages

:smiley:

Additional contributors and contributions stats

imagen

From the 100 contributors we got, 66% of them haven’t interacted with our localization tool (pontoon) in the past (new), and another 11% haven’t contributed more than 20 strings in the past year (casual).

imagen

It’s interesting to observe how the new localizers in addition with casual/inactive ones represented 77% of all contributors population and generated 40% of the total localizations. Good signal in terms of engaging new people and re-activate more casual contributors.

imagen

Also, new localizers represented 53% of the votes/reviews to existing suggestions, so while the existing localizers represented the biggest numbers in localizations, new localizers were more engaged in the review/voting process.

1 Like

Hi Ruben,

I would like to know if the download rate of the add-ons had been improved by the localization. Do we have any stats about that?

Hi Irvin,

Unfortunately we haven’t been able to promote the add-ons yet so we have paused the measurements until we do because we believe they will be highly influenced by the promotion.