Firefox L10n Report (Aurora 40)

Jeff Beatty


Hello localizers!

Thank you all for your great work with Firefox 38 and 39. Here’s an outline of what is currently in Aurora this cycle (40) and what we accomplished together last cycle:

This cycle (Fx40) — 11 May – 29 June

Key dates:
– Beta (39) sign-offs for new locales must be completed by 9 June.
– Beta (39) sign offs for already shipping locales must be completed before 16 June.
– Aurora (40) sign offs must be completed before 29 June.
– Firefox 39 released 12 May.
– Firefox 38.0.5 (Northern Spring Release) releases 2 June.

Remember that the schedule for the next few cycles is going to be odd. Here are the basics:
– May 11 – June 29 — This cycle will be 7 weeks in order to catch up to the regular schedule after cutting the Fx38 in Aurora cycle short by one week.

– Approximately 239 new string changes landed in Firefox Aurora desktop and 35 for Fennec Aurora exclusively (unshared).
– 40% of desktop string changes are related to devtools. 13% are related to e10s and add-ons. 9% are related to Firefox Hello and 10% are related to new tabs and new prefs. Please see for more info.
– 2 devtools files, ( and were moved from browser (browser/locales/en-US/chrome/browser/devtools) to toolkit (toolkit/locales/en-US/chrome/global/devtools). Tools like Pootle will automatically detect this change; if you’re localizing directly on Mercurial, you should move the files using ‘hg mv’. Feel free to ask more information on the mailing list or IRC (#l10n) if you need any help.
– 50% of the Fennec strings changes are related to tab queue management. ~30% are related to doorhangers firstrun, and onboarding, and prefs. ~20% are related to tab queues. 37% are obsolete strings that need to be removed from your repo.
– In addition to Firefox and Fennec, Firefox for iOS will launch it’s first version after the Northern Spring Release. I’m hoping to have more information about this next week.

Please remember that sign offs are a critical piece to the cycle and mean that you approve and can vouch for the work you’re submitting for shipment. For the 38 Northern Spring Release sign-offs, Axel and I made the decision to accept sign-offs for locales who had spent a long time trying to come up-to-date but have struggled to complete translation for all necessary parts. Our rationale was that it was better for a new user to receive the most up-to-date localization, even if that localization is only 80% localized, rather than a localization of Firefox that was 65% localized. If anyone has questions about this, please feel free to find Axel and I.

Last cycle — 30 March – 11 May

Noteworthy events:
82% of all locales shipped Firefox 38 on desktop updates on time. Congratulations to everyone who signed off and shipped this last cycle! This is a stunning 11% increase in locale coverage between Firefox 37 and Firefox 38! Hooray!
87% of all locales shipped Fennec 38 on time. Congratulations to everyone who signed off and shipped this last cycle! This is a stunning 12% increase in locale coverage between Fennec 37 and Fennec 38! Hooray!
– The Azerbaijani [az] team launched their first localizations of Fennec with Fennec 38. Please reach out to them with your congratulations!
– The Persian [fa] team launched their first complete localization update of Firefox desktop in nearly two years with Firefox 38. Please reach out to them with your congratulations! Here’s to many more Persian localizations of Firefox!

Thank you to everyone for all of your dedication and hard work this last sprint. As always, if you note anything missing in these reports, please let me know.

Mozilla l10n efforts to measure translation quality

Jeff Beatty


Measuring translation quality is a shared priority

Part of what makes Mozilla projects so unique is the involvement of the community. Our community prides themselves on being experts on the Web, Mozilla, and all of Mozilla’s products. Thus, delivering high quality localizations of Mozilla products to users is not only a priority for the l10n-drivers, but one that is close to the community’s heart. For something that we all care deeply about, we have trouble collecting the required data to measure and benchmark translation quality within Mozilla.

Why do we need to measure translation quality?

It’s in Mozilla’s best interest to measure translation quality for three reasons:

  1. Our l10n community rocks and everyone outside of Mozilla needs to know it! Community-based translation, as a practice, is often underestimated. We have tons of anecdotes that illustrate how dedicated, skilled, and talented our community is at weaving together the perfect translations for Mozilla projects, but we can’t measure a cool story. We’re out to collect measurable data that demonstrates how awesome our l10n community is, in addition to the stories we know and love.
  2. Our l10n community rocks and everyone within Mozilla needs to know it! This information could help key decision-makers within Mozilla when making internal decisions that have an impact the direction of product development.
  3. Our l10n community rocks and our localizers themselves need to know it! Many of us who have attempted to bring new Mozillians into the l10n community often mention that l10n is a good place to learn, grow, and develop skills. Unfortunately, without accountability or a standard way of measuring and certifying an individual localizer’s growth, that promise becomes meaningless. Regularly gathering this data in intervals would allow the l10n-drivers to benchmark translation quality and make good on the promise that a localizer can show the world that they’re awesome through participating in Mozilla l10n.

Currently, Mozilla has no criteria-based framework for evaluating a localization/translation’s accuracy or quality. Determining how to evaluate translation quality is a very difficult task because language itself is very flexible and subjective. Critical to creating a successful framework for evaluating translation quality is including elements of a project’s scope as well as the most objective pieces of language, such as orthography, grammar, and corporate style guide. A translation quality assessment framework would need to be flexible, robust, interoperable, and easy for graders to use. Developing such a framework is difficult, but there are efforts from standards bodies working to solve that problem.

Evaluating the options

Pilot projects are a good way for us to determine the most appropriate standard and accompanying toolchain to use within the Mozilla l10n program. In June, we’ll be running another pilot project to assess the translation quality of new strings between Firefox OS 2.1 and Firefox OS 2.2 in Spanish using two different standards and their accompanying toolchains. We’ll collect data from each, analyze their efficiency in providing actionable feedback for localizers, and determine which standard and toolchain to begin implementing within the l10n program. If you are fluent in Spanish & English and would like to help evaluate Firefox OS 2.2 translations with this project, we would love for you to get involved! Visit us in #translation-quality on IRC. If you’re interested in other opportunities to help with translation quality assessment projects, stay tuned to the l10n blog for updates.

Celtic Languages Meet-up



At the beginning of March I was able to attend a localization meet-up/hackaton hosted in the lovely city of Bangor, Wales. Besides being the home of good part of our Welsh localization team, Bangor’s university hosts a very active Language Technologies Unit working on fields like speech recognition, machine translation, language corpora, etc.
On Friday the meet-up was preceded by a conference, Through Technological Means (Trwy Ddulliau Technoleg), that aims to bring together academics and practitioners who have an interest in the use and proliferation of language technologies in minority languages.

The target of this event was to gather localization teams from several languages spoken in the area, in order to take them up to speed on the recent changes in Mozilla, discuss their successes and struggles, compare experiences and catch up with some localization work.

The event spanned over two days, with about 20 participants covering Breton, Welsh, Irish, Scottish Gaelic, Manx and Scots. A perfect match of old-guard locales with over a decade of experience, and new locales just starting to localize Mozilla products.

Celtic Meet-up Group

Photo by our fearless Mozilla Rep, Stephen Murphy

We started of with Mozilla’s mission: “Build the Internet as a global resource, open and accessible to all”. How can a product be really global, or even accessible if it’s not localized?
The localization of Firefox into Celtic and minority languages is a representation of Mozilla’s commitment to accessibility. As an open source project, everyday people take the fate of their language’s digital existence into their own hands and make Firefox a browser that esteems all the languages of the world equally.

We then moved to Mark Surman’s call to radical participation, and how important is to create a virtuous cycle where participation helps our products and programs, but at the same time people get value from participating.
It’s interesting to see what kind of values localizers are getting (or would like to get) from their contribution:

  • Being able to create connections with other people sharing the same passion for the language.
  • Being able to have an impact.
  • Being able to work directly with advanced technologies normally not accessible.
  • Coming from a linguistic background, learning practical IT skills.
  • Supporting local initiatives (e.g. localization academies).

It’s also important to remember that all these teams don’t simply work on localizing Mozilla products, but are often involved in localizing other Open Source projects like Libreoffice, KDE, etc.

Some interesting thoughts, and potentially actionable items coming from the meeting.

Download Page and Discoverability

The current download page for Firefox on relies exclusively on the current browser’s locale. If you’re using a browser set to en-US (American English), you’ll get a download link for the en-US version of Firefox.

It would be interesting to introduce geolocation in the picture: if you’re downloading Firefox from Bangor, the page should at least tell you that there are other builds you might be interested in for this area of the world. The same issue is relevant for other regions: think for example of a browser set to es-ES (Spanish from Spain) but used in Mexico, Argentina, or Chile, where we have specific localizations.

Printable and Localizable Marketing Material

We focus our entire communication on the “online”, but sometimes it would be useful to have material specifically created to be localized, printed locally and used in local events, or places like universities and libraries. And even keeping the focus on web content, we could do better in creating localizable campaigns. For example see this Libreoffice animation completely localized in Welsh.

Multi-language Support in Firefox

The current experience is far from good: you install an add-on (language pack) to add support for a specific language, but then you need another add-on to switch the UI language (or manually change preferences in about:config), and sometimes things break badly.

Multi-languages support is particularly important for minority languages: it’s not possible to install a browser in language X when there are multiple people with different language skills using a computer (think for example about universities and IT labs), sometimes that’s not even possible at home, where proficiency in a specific language might skip an entire generation.


Personally I found the event extremely fulfilling and useful. I hope it’s been an occasion for all participants to strengthen their bonds as Mozillians, and I’d like to thanks all people who spent energy and time in making this possible.

If you’re interested, some more links with further information and photos:

Virtual, global Mozilla l10n sprint — Report

Jeff Beatty


I want thank everyone who both accomplished their Spring Release work before the l10n sprint and participated in the l10n sprint. As you know, the Spring Release is one of the two major releases this year and a big opportunity for new users to download and install your localization work. When they do so, we want to make sure they’re installing the most localized version of the browser(s) yet! In order to be sure that your localization is one of those shipping an update in the Spring Release, please sign off on your projects by 30 April.

Here’s what we accomplished before and during the sprint:

Firefox 38 desktop:

  • pre-sprint 48% signed off,
  • post-sprint 53% signed off (rm, tr, fa, ko)

Fennec 38:

  • pre-sprint 64% signed off,
  • post-sprint 66% signed off(pt-PT)

Web parts:

  • eo, kn, bn-IN, sk were able to bring their and other projects up-to-date.

The following locales were done with Firefox/Fennec spring release before the sprint. Congratulations and thank you:

  • af
  • an 
  • ar 
  • az 
  • bg 
  • bn-IN
  • br 
  • cs 
  • cy 
  • dsb 
  • es-CL 
  • es-ES 
  • et 
  • eu 
  • fi 
  • fr 
  • fy-NL 
  • ga-IE 
  • gd 
  • hr 
  • hsb 
  • id 
  • is 
  • it 
  • kk 
  • lv
  • my
  • nl 
  • pt-PT
  • pl
  • ro 
  • ru
  • sk 
  • sl 
  • sq 
  • sr 
  • sv-SE 
  • uk 
  • zh-CN 
  • zh-TW

The following locales made progress on localizing Spring Release products (Firefox/Fennec) during the sprint. Thank you for your involvement:

  • bg
  • br
  • cs
  • de
  • es-MX
  • fa
  • hi-IN
  • kn
  • ko
  • lt
  • nn-NO
  • pl
  • pt-PT
  • rm
  • si
  • ta
  • tr
The Beta cycle is not yet over and we all still have time to ship the most linguistically accessible version of the Firefox browsers yet! If you have not yet signed off on your localizations, please do so by 30 April. We will be reaching out to individual locales between now and then to see how we can help you ship a complete update for Spring Release!

Awesome l10n contributor: Umesh Agarwal

Jeff Beatty


Part of a series similar to the Awesome L10n Communities series where individual contributors are spotlighted for their efforts.umesh

Umesh Agarwal

Started with Mozilla project: 2013
Nationality: Indian
Languages: English, Hindi, Bengali
Background: CS graduate specializing in Big Data and Data Mining, working on Oracle apps development.
Role in L10n community:  Translator & review for Hindi projects, coordinating Hindi Marketplace l10n
Projects you’re currently working on:
  • Marketplace
  • Other projects in need
  • Previously worked on Webmaker
How did you get started with the Mozilla project?

I began at Mozilla as a university student. Other members of the Indian community (Shahid Farooqui, Biraj Karmakar, Chandan Kumar) recruited me to be involved in the project. Shahid created an event at the university and gave me the chance to give a presentation on Mozilla design. After that event, Shahid conducted an online sprint for localizing projects in Pootle. Biraj and Shahid trained me on how to localize Firefox and other projects and then got me in touch with Rajesh Ranjan. Through Rajesh, I became familiar with the FUEL project and I became more and more involved. Seeing the software in my language was a very good and motivating experience.

What have been some of the biggest challenges to your localization effort?
It can be very difficult to find documentation for being involved in l10n. It is especially very tough for beginners. Connecting with mentors can help to fix this and make getting involved in Mozilla localization much easier and a lot of fun.


What have been some of your biggest successes?

Becoming a reviewer and then a l10n project coordinator for a national language (Hindi) in less than two years.

What’s your philosophy/method on localizing Mozilla projects (how do you stay on top of things)?

Having a clear priority for a project helps localizers to know where to concentrate all of our efforts and provide the best quality translation for the project. Take the Marketplace project, for example. When it became a priority and a need in India for the Firefox OS launches, we were able to focus on it. Before then, we didn’t focus on it. Prioritize your team’s projects within your own team. When another project priority is escalated, adjust. When there’s no escalation, rely on your team’s internal project priorities. Document these priorities on your team’s wiki page.

As a reviewer, I must also be a mentor. When I reject a string, I must follow up with them feedback on why that string was rejected to help them to improve their work and grow.

If you could identify several best practices that have helped you to become a successful Mozilla localizer, what would they be?
  • Follow the Mozilla L10n guidelines as closely as possible.
  • Following the guidelines from your regional l10n mentor.
  • Be in contact with your l10n mentor frequently.
  • Enjoy it! 😀
You’re a Mozilla Rep and a localizer. Do you see these roles as complementary? Could you provide details?

Both have their separate responsibilities, but in some ways they overlap. I’m able to organize localization events for Hindi, which helps the Hindi l10n community. As a Rep, my network goes beyond l10n, so I often help with events that aren’t l10n-specific. Where there’s a need from a specific l10n team to help, I’m able to support them with the Reps program, regardless of if it’s within the Hindi team or in another. I have helped with Bengali l10n events and the Maithili Fennec launch event in Patna.

What unique practices does the Hindi l10n team have for working on l10n projects?

We hold virtual l10n sprints, since the Hindi l10n community is spread throughout India. The Hindi mailing list helps to coordinate all of the work no matter where we are.
We also divide the workload and l10n project ownership. Many localizers want to be involved in Hindi l10n. It’s important to spread out the workload and give others an opportunity to participate and grow. Decentralized leadership also helps to mentor more people and share good ideas and practices.

What are you most looking forward to accomplishing this year in your l10n efforts?

With this month’s virtual l10n sprint, I hope that we can arrive at 80% complete in Pootle for the locale. I’m also really looking forward to reactivating the localization literacy map project in FUEL.

Five things you may not know about me:
  1. I’m helpful, but sometimes it comes off as arrogant because I’m unable to help when there are communication gaps.
  2. I’m the leader of the FSA task force leader in India.
  3. I just recently became a Reps mentor :-)
  4. I like soft Hindi music.
  5. My favorite food is biryani.

Virtual, global l10n sprint for Northern Spring Release

Jeff Beatty


Hi localizers!

Thank you for all of your work to make the Northern Spring Release a success. Because the timeframe was so brief for localizing 38 in Aurora, we’re asking that you continue to focus your efforts on making 38 a great release while it’s in Beta. The marketing and publicity that will be used to promote this release will be critical to gaining more users across all locales and platforms. To best serve Mozilla users at this important time, we need to be sure that they receive the best the community can offer in localized products.

That being said, I’m excited to announce that we’re trying something new and different than what we’ve done before. On 8 April, we will be holding a virtual global localization sprint for the Northern Spring Release! We feel that the opportunity for user growth provided by the Northern Spring Release creates an exception to the preferred way of localizing these projects and requires this rare event. I use the term “sprint” specifically because we are hoping to cover a lot of l10n work within a short, 24-hour period of time in Beta (essentially, we’re sprinting to cover a lot of ground, fast). Here’s what will be involved:

– Unify the global l10n community virtually for 24 hours in order to complete l10n work associated with the Northern Spring Release (Fx38, fennec38, fx-ios, marketing, fxOS2.2, marketplace).

How it will happen:
–  A few l10n-drivers will clear their schedules throughout the day on 8 April starting at 12AM UTC. Each will work exclusively to support those participating in the sprint by answering questions, helping with testing, performing sign-offs, and even jumping in to translate where you feel it would be helpful.
– We have created the localization channel in vidyo just for this event ( and will hold most of the discussions there and in #l10n.
– There is no schedule of sessions or topics; this will be simply the largest online gathering of localizers around the globe intent on translating Mozilla projects for the Northern Spring Release.
– We’ll publicize the sprint on social media using the hashtag #mozl10n.
– While the sprint will be going on during those 24 hours, no one is expected to stay for the full 24 hours. We’re simply asking that you plan to spend time with us that day translating together.

Please join us on 8 April for this rare event for the Northern Spring Release! And please forward this email along to all members of your l10n team.

Please also let us know if you have any questions.

Looking forward to seeing you there!

Localize Firefox 38: Northern Spring and ESR!

Axel Hecht


Firefox 38 is now string frozen. On March 30th, we’ll migrate 38 to
beta, which gives you a week and a half to get the translation work into
a great state.

This is one of our two big releases this year, and it’s the ESR, so it’s
going to be around for a while.

We ended up with a good 300 strings for 38; they’re split across:

  • Reader View and Reading List
  • Hello (tab sharing for example)
  • Developer Tools

Upcoming schedule for 38 and the northern-spring release:

  • March 30: Migrate from aurora to beta
  • April 6: Marketing material string freeze (including content for
  • April 30: last chance to get changes in on beta
  • May 12: Release Firefox 38, and celebrate

We’ve been talking to Dwayne about opening up 38 on Beta on locamotion,
and giving you all the goodness there. He’ll follow up on that.

Thank you so much for your contributions and your patience.

Localization Hackathons in India and Sri Lanka

Jeff Beatty


In February, three of the l10n drivers were able to make an overdue trip to meet with localizers in India and Sri Lanka. It was a really wonderful experience to meet localizers in person that we had interacted with for so long virtually.

We had a particular format for the event and a few specific goals. The format was to spend half of each day in large group discussion and half broken up into each l10n team so that localizers could fix bugs, translate strings, and collaborate in person while we discussed l10n community health status with each l10n team, one-on-one. Unfortunately, this format was slightly confusing the first day, particularly the breakout half of the day. The second day was much more productive. Our goals for the meetup were specific to matters in India localization communities:

  1. Share updates to product release schedules and the Mozilla organization with localizers.
  2. Discuss how localizers see their localized products being used in India and Sri Lanka and brainstorm how to increase the user base for Firefox and Fennec in local languages.
  3. Discuss how Indic and Sri Lankan localization teams prioritize localization work.
  4. Identify outstanding internationalization bugs that specifically affect Indic languages.
  5. Create a strategy to raise the number of Indic languages we ship Firefox into from 12 to 22.

We were able to accomplish each of these goals and enjoy the collaboration with the community to do so. We learned a lot of helpful insights into the challenges faced by Indic l10n teams.

There were three discussions that were particularly engaging: the virtuous participation cycle, the Mozilla l10n landscape, and increasing the user base for Firefox and Fennec in local languages. One of the most interesting outcomes of these discussions was the creation of a local language promotion taskforce in India. This taskforce is responsible for creating campaigns to educate users on how to find Firefox and Fennec in their local languages and to help Mozilla identify successful marketing strategies for increasing the local language user base in India.

In Sri Lanka, we had a great opportunity to meet with both new and veteran localizers for the Sinhala localization team. In addition to a very engaging conversation about how people in Sri Lanka use Firefox in Sinhala, the most interesting and motivational part of the hackathon was the breakout portion. Seeing veteran localizers become very involved in mentoring new localizers and collaboratively creating a Sinhala style guide and glossary was inspirational.

All-in-all, this was a very fulfilling experience for Axel, Arky, and I. I want to thank Ani Peter, Rajesh Ranjan, Galaxy Kadiyala, Danishka Navin and Konstantina for all of their help to make these events possible and successful.

For more information about these events, please see the following links:


Here are some of our favorite pics from the events:

2015-02-02 14.57.33 2015-02-03 15.43.12 2015-02-03 17.00.16 2015-02-03 17.28.53 2015-02-05 11.04.33 2015-02-05 13.29.06 2015-02-05 14.02.58 2015-02-06 12.13.25 2015-02-06 17.07.142015-02-08 13.59.36 2015-02-08 14.00.07 2015-02-08 14.22.31

Firefox L10n Report (Aurora 37)

Jeff Beatty


Hello localizers!
Thank you all for your great work with Firefox 35 and 36. Here’s an outline of what is currently in Aurora this cycle (37) and what we accomplished together last cycle:

This cycle (Fx37) — 13 Jan. – 24 Feb.

Key dates:
– Beta sign-offs for new locales must be complete by 2 Feb.
– Beta sign offs must be completed before 9 Feb.
– Aurora sign offs must be completed before 23 Feb.
– Firefox 36 releases 24 Feb.

– Approximately 97 new string changes were made to Aurora desktop, 20 for Aurora mobile exclusively (unshared).
– 37% of the desktop strings changes are in devtools. 46% are strings that need to be removed from your repo. The rest are related to mixed content, search UI, and mirrored tabs. (see for more info).
– 60% of the mobile string changes are related to syncing your Firefox account. 10% of the mobile string changes are related to password security. The rest include the home page and pref tracking protection (see ).

Please remember that sign offs are a critical piece to the cycle and mean that you approve and can vouch for the work you’re submitting for shipment.

Last cycle — 1 Dec. – 12 Jan.

Noteworthy accomplishments:
62% of all locales shipped Firefox 35 on desktop updates on time. Congratulations to everyone who signed off and shipped this last cycle! This is an 8% decrease in locale coverage between Firefox 34 and Firefox 35.
76% of all locales shipped Fennec 35 on time. Congratulations to everyone who signed off and shipped this last cycle! This is a 1% decrease in locale coverage between Fennec 34 and Fennec 35!
– The Breton (br) and Esperanto (eo) teams launched their localizations of Fennec with Fennec 35. Please reach out to them with your congratulations!

Thank you to everyone for all of your dedication and hard work this last sprint. As always, if you note anything missing in these reports, please let me know.

Firefox L10n Report (cycles 35 & 36)

Jeff Beatty


Hello localizers!

Thank you all for your great work with Firefox 34 and 35. Here’s an outline of what is currently in Aurora this cycle (36) and what we accomplished together last cycle:

This cycle (Fx35) — 1 Dec. – 12 Jan.

Key dates:
– Beta sign-offs for new locales must be complete by 22 Dec.
– Beta sign offs must be completed before 29 Dec.
– Aurora sign offs must be completed before 12 Jan.
– Firefox 34 releases 13 Jan.
– Approximately 192 new string changes were made to Aurora desktop, 39 for Aurora mobile exclusively (unshared).
– 40% of the desktop strings changes are strings or files that need to be removed from your repos. 8% of all changes are related to Loop. 40% of all string changes are in devtools (see for more info).
– 28% of the mobile string changes are related to Do Not Track. 15% of the mobile string changes are related to Content Security Policy. The rest include home page, Firefox Accounts, and preferences (see ).

Please remember that sign offs are a critical piece to the cycle and mean that you approve and can vouch for the work you’re submitting for shipment.

Last cycle — 13 Oct. – 1 Dec.

Noteworthy accomplishments:
70% of all locales shipped Firefox 34 on desktop updates on time. Congratulations to everyone who signed off and shipped this last cycle! This is an 10% decrease in locale coverage between Firefox 33 and Firefox 34.
77% of all locales shipped Fennec 34 on time. Congratulations to everyone who signed off and shipped this last cycle! This is a 3% increase in locale coverage between Fennec 33 and Fennec 34!

Thank you to everyone for all of your dedication and hard work this last sprint. As always, if you note anything missing in these reports, please let me know.