Some numbers of the campaign’s day 4
Congratulations to Chinese, which already have all suggestions covered, now they are in the review phase, voting suggestions to help core localizers approve the final strings.
Keep the great work! 
I see also people adding comments on the strings on Crowdin but no reply to them so they work on the other strings and this pending remain incomplete.
Some numbers of the campaign’s day 7
Chinese just needs to validate all the complete suggestions. Spanish, Dutch and Italian are close to complete all suggestions, German and French follow close.
Russian, Portuguese, Polish and Japanese need a big push, we are just one week away of the end of the campaign.
Keep the great work!
PS: Great job for italian during the weekend btw! 
Congratulations to Spanish and Portuguese! They are now ready for review.
But remember, we still need to keep voting strings in the review mode to help approvers with the final check, this is as important as suggesting strings 
PS: Dutch is close to complete all suggestions and Japanese, Polish and Russian still need more people involved!
Some numbers of the campaign’s day 9
Spanish, Dutch, Portuguese and Italian did an amazing work in the past days, completing their suggestions. Russian, Portuguese, Polish and Japanese still need a big push.
Important: Remember that having all suggestions is not enough to validate your language, please keep voting for good suggestions in the review mode, core localizers rely on these votes in order to speed up the process and approve the final strings (green bar in the graph below).
Keep the great work, and remember to vote strings!
Some numbers of the campaign’s day 11, just 3 days away until the end of the campaign
Chinese, Dutch, Italian, Portuguese and Spanish are approving the final strings, excellent work from these communities.
French and German still need a final push if they want to get in time for the end of the campaign, if you know the language please chime in and help today!
Unfortunately Russian, Japanese and Polish haven’t got a lot of contributions and are still mid-way with the suggestions. If you are in these locales, please organize a day during this weekend to suggest and vote strings.
As I previously commented, we are 3 days away from the final date, July 2nd, where we will start generating the Add-ons for testing only for the locales that have all strings approved.
Thanks to everyone who has been involved so dar!
PS: Special shout out to @philipp (German) and Tonnes (Dutch), @sara_t (Italian), Breaking_Pitt (Spanish) and @xcffl (Chinese) who made a huge push in their languages progress during the last 2 days
I’ve updated the first post with the upcoming milestones for this project:
Hi,
Today is the last day, is there still translation to be done?
Thank’s
Christophe
For French I see that just a few approvals are needed, almost there. @theo and @benoit.leseul were coordinating there
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 
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!
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!
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.
I’ll be providing a more detailed report in the coming days.
why are we not doing localization in Hindi?
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
about:debugging in a tabmanifest.json from the add-ons folder where you extracted the zipabout:addons
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.
Thanks for the great work this week testing and reporting issues with the add-ons and correcting the misplaced strings
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
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
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:
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.
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/
