Mozlando Localization Sessions

Jeff Beatty


Twice per year, Mozillians from around the world are invited to attend All Hands work week. All Hands is an opportunity for both paid and volunteer staff from all functional areas to meet together to solve problems, brainstorm new goals, and find ways to make the Mozilla mission a reality. For the localization functional area, All Hands gives us a chance to collaborate on resolving challenges in the l10n process, discuss community needs, and start new programs within the functional area. Below is an overview of the highlights and l10n-specific sessions that were held in Orlando. More information about many of these sessions will be made available in the coming weeks.

General updates

Firefox OS moves to connected devices

One of the main announcements from the Mozilla executive team was Firefox OS’s new focus: connected devices (for more info on the move, please read ). Exploring the Internet of Things (IoT) space with Firefox OS will require a lot of experimentation, which leaves a lot of open questions. What we know for sure is that we will not be pursuing commercial smartphone distribution partnerships with Firefox OS. Until we understand what will will be involved in the IoT connnected devices experimentation, we recommend deprioritizing Firefox OS localization.

Focus by Firefox

Focus by Firefox was launched on stage during the first plenary session at Mozlando (for more info, please read ). Focus is a content blocking app for the iOS platform, consisting of a set of preferences that filters the content a user sees across a variety of iOS apps. The team is currently determining the product’s direction for 2016; we’ll incorporate localization as the opportunity presents itself.

L10n sessions

Updating our communication strategy

Review of our communication channels, their audiences/purposes, and where we can improve on capturing localizers’ attention. Exploring cycle times, automated push notifications, calendaring, broadcasting rates, single-source authorship, multi-platform, event-based, social publishing, etc.

Thanks to all of you who took the communication channels survey, this discussion was very well informed. The results from that survey taught us that there are a lot of things we seem to be doing well, as well as a few things that we can do better with our l10n communication strategy. We agree with many of you that further splintering our l10n messaging will certainly be damaging to our ability to carry on a unified conversation. We recognize, however, that there are opportunities to enhance our communication for specific purposes. We plan to begin a bi-monthly video call for anyone within the l10n community that would like one-on-one training from the l10n-drivers, as well as clarifying any questions about product and l10n tool roadmaps. We also plan to continue to use Telegram to coordinate multilocale l10n hackathons in the days leading up to the events and during the events themselves. We also know that it can be difficult to filter content coming through the dev-l10n mailing list to what is more relevant to you. We plan to help your email filters by implementing a series of easily identifiable subject line keywords that categorize our messages in the mailing lists. More about that will be coming in the following weeks.

Removing some of the training burden

Many l10n teams struggle to train newcomers and instead opt to not recruit and instead take on more work than they can handle. What can l10n-drivers do to help mitigate some of the training burden?

This discussion was one example of how useful the All Hands work weeks can be to facilitate collaboration between localizers and l10n-drivers. As described above, we wanted to brainstorm solutions to the problem of how we make the process of training newcomers less challenging for existing l10n communities. As one localizer noticed, “[We discussed] the need to reduce friction for new contributors [and] to keep existing ones and to further train and invest in existing members. This can be accomplished on the social side by promoting friendlier interactions between members, on the technical side with easier-to-use tools, but also swag (gear, t-shirts etc) and periodically sponsored events.”

Coming away from this discussion, we identified the following as ideas that we can experiment with to make training newcomers easier:

1) Create a standard method of training newcomers across all locales.
2) Update existing documentation, replacing most of it with task-oriented video tutorials with translatable subtitles and a native English-speaker for audio clarity.
3) Set up staging servers for l10n tools like Pontoon and Pootle to teach newcomers to properly use these tools and create interactive tutorials.
4) Create a translation competency test based on already translated materials to test newcomers’ skills with manual review/scoring from existing communities. Eventually moving toward an automated review/scoring system based on existing methodologies.

Pontoon video tutorials are coming and we’ll be consulting with localizers to create more video tutorials on necessary l10n tasks.

Pontoon: planning with localizers and devs

In 2015, most localization teams started using Pontoon thanks to Verbatim migration, automated repository synchronization and being able to localize all projects in one place. For 2016, we’ve identified 3 focus areas: extending support for in-page localization, making product localization more comfortable and improving overall user experience. In Orlando, we started collecting more concreate ideas to get down that path, which you can find on the Etherpad ( They will be moved to Bugzilla and prioritized soon.

Translation quality scorecard: where to go from here

Discussion of MQM standard, tool SWOT (Strengths, Weaknesses, Opportunities, Threats analysis), planning of next phase and 2016 roadmap for program implementation

In this discussion, we reviewed the experiments we have performed with translation quality metrics and the direction that we need to go within 2016. Quality is a primary point of focus for 2016 and standardizing our methods of performing translation quality and measuring that output is a critical component to informing decisions we make concerning l10n in the future. Focusing on using the Multidimensional Quality Metric standard as the basis for standardizing translation quality metrics, we discussed some formal methods of measuring the quality of translations. A large portion of the discussion also centered around making it easier for l10n communities to create style guides and termbases (or bilingual glossaries). We’ll be discussing more about these soon in dev-l10n.

L10n community hackathons: 2015 post-mortem, 2016 strategy & How to execute a l10n hackathon

Discussing 2015 and 2016 l10n community hackathons and global meetups & the step-by-step process of organizing a regional l10n hackathon + creative brainstorming for overcoming common challenges within that process.

The slides from this session will be shared on dev-l10n shortly. We reviewed the overall impact of the 2015 multilocale hackathons. In 2015, the aim was to have the l10n-drivers organize enough multilocale hackathons to enable us to meet with localizers from each of Mozilla’s 90+ l10n communities. In 2016, we aim to take a much more collaborative approach to organizing these by working with l10n communities to improve upon these meetups. Finally, in 2017, we hope that l10n communities will take the reins to organize their own meetups throughout the year and invite l10n-drivers to attend. We established a first draft schedule for 2016, as well as a detailed plan for how to collaborate more with l10n communities in organizing these hackathons.

FFOS Strategy in Africa and challenges for reaching new locale users on Mobile

Coleman Donaldson (a language activist and linguist and former peace corps volunteer) talked about the challenges faced by localizing in African languages, many of which were only recently written, or not at all. By supporting localizations in these languages, Mozilla is making a major contribution to those languages and cultures and being first (or often the only) organization willing to offer them devices localized for them. Hundreds of millions of people will have access to their own computing device and Mozilla wants to be first to deliver software for those devices in those local languages. Right now, most people have phones localized for French or English and pushing for a local language offering is a chance to distinguish Mozilla as a champion of local languages and also kick-start more local communities. Mozilla’s most valuable asset in that endeavor is the community.

Firefox and Localization

Firefox Architects, Product, and the L10n team are aligned on Localizing Firefox in 2016.

We discussed Firefox l10n in 2016, which deserves a post of it’s own. That will be out in the near future.

As you can see, there are a number of big changes coming for 2016. We will do all we can to keep everyone informed. As always, if you have any questions about these topics, the sessions, or All Hands in general, please feel free to ask. Thank you to all who attended and made it a priority to participate actively and represent your l10n communties so well. Please remember to share your experience and what you accomplished while in Orlando with the rest of your l10n communities.


Demo-ing and providing feedback on the latest improvements to Pontoon.

Firefox l10n report (Aurora 45)

Jeff Beatty


Hello localizers! 

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

This cycle (Fx45)

Key dates: 
  • Beta (44) sign offs for *already shipping locales* must be completed before 13 January
  • Aurora (45) sign offs must be completed before 25 January
String breakdown:

Last 2 cycles

Noteworth events (42):
  • 84% of all locales shipped signed off updates of Firefox 42 on desktop. This is a massive 17% increase in locale coverage between Firefox 41 and Firefox 42!
  • 80% of all locales shipped signed off updates of Fennec 42 on Android. This is a 6% increase in locale coverage between Fennec 41 and Fennec 42!
Noteworthy events (43): 
  • 66% of all locales shipped signed off updates of Firefox 43 on desktop. This is an 18% decrease in locale coverage between Firefox 42 and Firefox 43.
  • 62% of all locales shipped signed off updates of Fennec 43 on Android. This is an 18% decrease in locale coverage between Fennec 42 and Fennec 43.
  • We’re also looking forward to seeing the Lao and Romansh localization teams launch their first Mozilla localizations in Firefox for Android soon.
Congratulations to everyone who signed off and shipped this last cycle! 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 Turkic l10n Meet-up – Istanbul



At the beginning of October, Axel and I took a trip to Istanbul to organize a new l10n hackathon. Is there a more iconic place than a city extending over two continents, with such diversity of culture, to host a localization event?

The target for these meetings is to gather key l10n contributors in the region, bring them up to speed on the latest updates regarding Mozilla, and understand their team’s health and perspectives.

At this event, hosted by a local hacking space named Iskele47, we had representatives from five languages: Azerbaijani, Kazakh, Russian, Turkish, and Uzbek.

Mozilla Turkic Meetup - Istanbul Oct 10-11

As usual for these meetings, localizers can have very different experiences, with a contribution history ranging from 11 years – Alexander, our Russian localizer – to brand new l10n contributors like Halil for Turkish.
Sometimes English can represent a barrier in our discussions, and a huge thanks goes to Emin, our Azerbaijani localizer, not just for being crucial in organizing the event, but also for acting as trait d’union through English, Turkish, and Russian.

Having participated in five of these meet-ups so far, it’s interesting to try and find common trends and differences:

  • Some teams feel part of Mozilla, others don’t feel this connection at all. The latter is common for localizers working on several Open Source projects, whose contribution to Mozilla started through external localization tools after what I call our “MozCamps phase.” In this sense, these local events are crucial to make them feel part of the broader community at the base of Mozilla.
  • Training new localizers is hard, time-expensive, and not really exciting: there are less technical issues than in the past, but ensuring consistency and high quality across many projects is really complex.
  • Finding new volunteers in some regions is more complicated than in others: big tech companies opening new offices and attracting students right out of school and professional localizers not liking the idea of contributing to projects for free can present obstacles.

There’s one result that I’m particular proud of, and represents the kind of practical outcomes we want to see from these initiatives: right before Istanbul, together with Baurzhan we realized that there was some confusion about the localization process for and Kazakh.
We decided to talk about it and fix it during the meet-up. This is the result of this process: from almost a thousand strings missing to zero.

Kazakh Webparts Status

If you’re interested in more details about this meeting you can read the meeting notes or check a few more photos.

Growing Communities Around African Languages (and beyond…)



(Blog post by Théo Chevalier)

Firefox OS is distributed across several countries and quickly expands throughout Africa. For many people, Firefox OS devices will be their first phone. This was an opportunity for Mozilla to provide phones in languages that are too often ignored or not well supported by other companies.

For many people, it will also be the first time they can get a phone that speaks their language. We are excited about it, localizers are excited about it, everyone is excited about it. With the recent addition of new African languages, Firefox OS 2.2 supports up to 97 languages – 40 of which are complete translation-wise!

From our own experience, we learned that building communities of localizers in Africa is extremely hard, and we failed many times. Even running on-ground events cannot guarantee people will be able to work together on the long term. We realized that connectivity is a major issue, though not the only one.

So during the summer we reached out to several people – most of them come from an Open Source background and have contributed already to other projects – explaining to them what we were trying to achieve with Firefox OS in Africa. We provided them communication channels and general support to start localization activities and get them up and running. We’ve been amazed to see communities growing up, especially around three languages: Bambara, Malagasy and Wolof.

We’re very proud of this for many reasons:

First of all for many African languages, Computer Science is very new in their culture – so the language itself is not yet adapted and a consensus must be reached for those terms. This can really slow down the translation, and launching new devices with partners means meeting strict deadlines.

Because of the lack of communities – and because of the deadlines – we sometimes have been forced to hire an agency to do the initial translation even though this was against our principles: all the translations at Mozilla are maintained by volunteers from around the globe. But we’re glad to see that now we’re back on track!

Connectivity in Africa is a major issue that can also slow down the process. Although the translations are mainly done online, our tools do offer features to work offline. However the work must be committed from time to time and team members must then coordinate. It’s not easy to take a decision or get in sync without connection when you’re not in the same city.

On the technical side, some languages may also require specific fonts in order to be displayed on the device — and given the nature of the project, the fonts must be redistributable and compatible with the Mozilla Public License 2.0. Sometimes, the glyphs don’t even exist, so we have to design them for the font used in Firefox OS. This involves Mozilla legal and User eXperience teams.

Another aspect to take into account in order to ship a new language is a dictionary. To provide features like auto-completion or auto-correct, Firefox OS must have a list of common words used in the user’s language — we call it corpus. For some African languages, it’s a real challenge to gather such corpus, as the language is sometimes mainly spoken and rarely written.

Finally, the biggest challenge comes when the language has very few speakers. It’s been very challenging to find volunteers willing to translate software in this case.

What’s been done

Those communities are new but already had achievements!
The Wolof team has worked with the MQM tool [ ] and have completed MQM sessions to assess the quality of the Firefox OS translation provided by the agency.

The Bambara and Malagasy teams have started localizing Firefox OS and are currently working with the agency to get the initial release complete in time.

What’s next?

All the teams will drive the localization of upcoming Firefox OS releases in their language! This is a great step forwards and very promising for the future of these languages in Africa.

Let’s now introduce some of the members:


Mariot Tsitoara

I’m Mariot Tsitoara, 22 years old and currently I am a mobile and web developer.
I’m passionate about video games (especially Legend of Zelda), Sci-Fi or Epic books (A song of ice and fire) and robots construction!
I was involved in Ubuntu but now I’m focusing on Mozilla and my personal projects.
I’m motivated in localizing products in Malagasy because I believe that everyone should have access to technologies and especially the web. Languages should not be a barrier. I have an opportunity to do good and it’s my responsibility to help make the world and the web a better place.
I can plug in an USB drive on the first try!


Imhotep Djehouty BAKHOUM

I’m Imhotep Djehouty BAKHOUM, I’m Senegalese and I live in Ngor (a village where mainly Lebou are living). I am a developer specialized in mobile development (Android, Kivy Python, etc.), web and desktop development with Java, Python, etc. I am passionate about community mapping, and an active member of the Google Map Maker community, in which I was a leader for many years. I also got involved in the Google Translate community. I’m feeding off of African culture (Kamite), traveling, meetings and discoveries. I’m highly motivated to help translating in Wolof, because it’s our language, it’s beautiful, has a lot of potential, and must be developed in all areas, including the most specialized, to better serve us.


Ibrahima Fall

I’m Ibrahima Fall, I live in Bologna, Italy. I have a degree in automation engineering. I am specialized in development of automatic systems (PLC, micro-controllers) and web platform (Java). I work as a software developer. I am, since 2007, the main contributor and administrator of Wikipedia and wiktionary in Wolof. Author of a hundred Wolof articles on Wikipedia. I translated the interface Wikipedia and associated websites in Wolof. My main motivations are allowing Wolof speakers to access the knowledge they need in their own language and to make learning easier.

Shipping new languages in Africa is a long journey, but you can help us! Please help spread the word. If ever you know people speaking African languages (even if we already support this language in Firefox OS), get in touch with the Mozilla Localization Drivers team via e-mail [] or Twitter (@mozilla_l10n), and you might actually help us create a new community of volunteers who will change people’s lives!

Mozilla RTL L10n Hackathon

Jeff Beatty


Arky, Delphine, Peiying, and I have just returned from spending a spectacular week at an event that is a first for the Mozilla Localization community: a gathering for Right-to-Left (RTL) localization communities! This was a very unique event, not only because it was the first hackathon dedicated to RTL issues, but it was also one of the few hackathons we’ve arranged outside of any of the RTL localization communities’ home countries. The Sinhala localization team hosted the event and were very welcome LTR participants within an otherwise RTL event.

A unique event

Never before have we been able to organize an event specifically for RTL. Being gathered together in Sri Lanka created a very unique opportunity to hear about RTL issues from a variety of perspectives. Additionally, being that half of the Persian l10n community is based in Iran, none of us had previously had the chance to meet and spend time with them. We were very fortunate to bring our Iranian Mozillian friends to this event and learn of their efforts to localize Firefox into their native language. Finally, we were pleased to organize the first meeting of the complete Urdu l10n community. I use the term “complete” because the Urdu l10n community is spread across India and Pakistan. They had made attempts to gather together in the past, but had been unsuccessful. Meeting in Sri Lanka gave us this opportunity and the full team was happy to be together for the first time.

RTL l10n communities at Mozilla

Firefox desktop is the only Mozilla product that has RTL support explicitly developed into it. Over the years, RTL support has been a desired feature in Mozilla’s mobile products, but our expertise and sustainable plans for it have not been able to culminate in fully supported RTL Fennec or Firefox OS products. Firefox OS has inched closer and closer to this reality and many within the Arabic and Urdu communities have dedicated time to testing RTL bugs and improving the support within that platform. We organized this hackathon for two reasons: 1) to include these locales in the list of teams we aimed to meet with in person during 2015; 2) to bring RTL localizers/users together in a room to triage bugs, learn how to test RTL issues, and establish a taskforce to be more involved in RTL across multiple Mozilla projects.

RTL hackathon activities

The agenda for this hackathon can be found in the Mozilla wiki. Within the wiki, you’ll find the agenda, as well as all of the etherpad notes that were taken during the event. These notes not only covered the morning discussions, but also provide an overview of the Arabic, Urdu, Persian, and Sinhala l10n community status as of October 2015. The agenda covered many of the same topics that (if you’ve been following along throughout the year) can also be found on the agendas of other hackathons. The key difference between this hackathon and others was how the free time in the afternoon was spent. Nearly all of the l10n teams participating in the hackathon were up-to-date on their product l10n projects for the 42 release. During their free time, they localized web parts content, initiated new l10n projects (e.g., the Persian team started localizing Firefox OS 2.5), and formed an RTL taskforce.

RTL taskforce

It has become obvious to the various RTL communities that the creation of an RTL task force is needed in order to drive the RTL effort onwards.Participants (mostly developers) from Arabic, Persian and Urdu teams have agreed that the RTL task force needs to be first and foremost a global task force – and that they can then address the possible RTL differences from one language to another as they come.

We have started to form a couple goals for this task force:

  • Planning and working on creating a seamless RTL experience across Mozilla products
  • Identify and study possible differences in RTL across languages
  • Fixing bugs in Fennec: RTL tracker bug for RTL Fennec for Android —
    • Finding and filing bugs in Fennec
  • Fixing bugs in Firefox OS current master- Meta bug:
    • Finding and filing bugs in FirefoxOS (under FirefoxOS > Gaia:component)

In order to get everyone on the same page and start working actual dev work, we have agreed that an RTL hackathon should take place soon, in order to have presentations on best coding practices and then do some hands-on bug fixing. This will also be the opportunity to define and prioritize the RTL task force’s goals.

With the creation of this task force, our next action items are to create tools to support this community (irc channel, wiki pages, mailing list, etc). Please stay tuned for progress on this great initiative!

Our host country & community

The Sinhala localization team in Sri Lanka was an amazing host community. They helped to select our accommodations, introduced us to delicious Sri Lankan food, and even took us site seeing and shopping. They introduced us to their culture, their home, and even brought us out to witness a large, 4-hour long Buddhist parade through Colombo which included Asiatic elephants! Peiying even got to pet one 😉 We had a great time and look forward to the Sri Lanka community inviting us back.

2015-10-03 13.16.10 2015-10-03 22.10.41 2015-10-04 16.59.59 2015-10-04 16.49.45 2015-10-04 16.24.00 2015-10-04 16.23.10 2015-10-04 16.23.39 2015-10-04 16.23.51 2015-10-04 16.23.32 2015-10-04 16.23.23 2015-10-04 17.07.43 2015-10-04 12.31.17 2015-10-04 12.31.22 2015-10-04 12.31.33 2015-10-04 12.31.39

Mozilla LATAM L10n & QA Hackathon 2015

Jeff Beatty


In a previous blog post on my personal blog, I described the unique sentiment that carried through the LATAM hackathon we held in Lima, Peru in June 2015. I won’t rewrite that here, but I think that Delphine, Guillermo Movia, and Juan Becerra would agree when I say that the event seemed to represent the bringing together of old friends to serve those users who spoke their native languages; whether all of these Mozillians were friends before this event or not, they all left with a depth of friendship that usually requires years to forge. It was truly special to be a part of and see how localization could bring together people from over 2 different continents.

This blog post is actually quite late, but doesn’t make it less important. As with other l10n hackathons, the agenda followed the same format: group discussion in the morning, free time in the afternoon. The discussions were phenomenal! Thanks to Marcus Saad for being our notetaker, we have all of the discussion notes (in an etherpad) linked to the hackathon’s wiki page.

This time around, I want to highlight what I felt were some of the most noteworthy accomplishments by the l10n group in both discussion time and free time:

Discussion time:

– L10n tool workflows were successfully understood by all present. This led to some with more technical skills becoming interested in hacking on Pootle and helping to resolve outstanding bugs within that system.
– Sustainable l10n team organization was explored in a variety of different ways. We discussed what a successful team org could look like for small (1-2 people), medium (5-6 people), and large l10n communities. We also discussed that there are always ways to make room for new localizers within a team’s organization through project, module, and rights assignment.
– Concerns about l10n workshops and interactions between localizers and Mozilla Reps were discussed, with ideas of how to improve and strengthen those relationships.

Free time:

– All locales presently shipping official l10n projects were able to sign off on products and focus time on web parts l10n.
– Mozilla Nativo v1.2 was born! Their purposes and goals were refined, having committed to change their strategy away from focusing on recruitment of l10n teams for all indigenous Latin American languages and toward focusing on sustaining and supporting 5 existing teams through the process of shipping their first localizations.
– Some ideas about creating l10n workshops in Brazil were discussed, with timelines for how to introduce these ideas to the Brazil l10n team as a whole.
– The Maya Kaqchikel team was tasked with identifying a launch version goal for their localization of Firefox for Android.
– The Zapotec l10n team was able to have repos and automated builds set up for their l10n of Firefox OS.
– The Paraguayan Guaraní and Bolivian Guaraní l10n teams were able to meet and compare both similarities and differences between their languages and their efforts. The Paraguayan l10n team came away with a strong strategy for approaching their l10n work with sustainability in mind (creating l10n resources first, as well as empowering more community members with reviewer and translator rights).

These lists certainly do not contain the full list of what was completed or accomplished by meeting together, but the time was certainly well spent. Our Peruvian hosts were incredible. Absolutely incredible. We sincerely thank the Reps in Peru for their support and involvement. This event couldn’t have happened without you.

Here are some photos taken at the event. Credit goes out to Juan Eladio Sanchez for his fantastic photo skills :-)

19111238633_3231555408_o 19543844378_f3e6ab480b_o 19544158698_fafde8e562_o 19544176210_6105ca1ff8_o 19544221200_c24ef2a598_o 19544242590_cb73cfaa54_o 19544254980_7bdf300719_o 19544268588_15a19fc3e5_o 19545233249_6c8030b024_o 19545369459_14a491d830_o 19545433289_647e696bd4_o 19545717079_e85d15de57_o 19705923136_4e4cd3012a_o 19706104776_d256639fa3_o 19724992162_f9f2505b70_o 19732190545_65d8cb1cb0_o 19736817071_d612230e45_o 19736855181_0c49da33bd_o 19736855971_300b1f721c_o

Firefox l10n report (Aurora 43)

Jeff Beatty


Hello localizers!

Thank you all for your great work with Firefox 41 and 42. Here’s an outline of what is currently in Aurora this cycle (43) and what we accomplished together last cycle. Note that in light of what we learned with the report’s information last time, we’re attempting to improve how we identify new strings each release. If you see something that seems off, please call it out:

This cycle (Fx43) — 22 September – 2 November


Key dates:
– Beta (42) sign offs for *already shipping locales* must be completed before 21 October.
– Aurora (43) sign offs must be completed before 2 November.

– Approximately 165 new string changes landed in Firefox Aurora desktop and 49 for Fennec Aurora exclusively (unshared).
– 35% of the new strings in desktop are in devtools and DOM. 21% are for the Firefox Hello client. 12% have to do with preference menu settings. Please see for more info.
– 27% of the new strings in Fennec are related to Firefox Accounts. 16% are for the Fennec first run screens. 14% are about bookmarks. Additionally, this bug may be breaking string freeze soon – .Please see for more information.

Last cycle — 11 August – 21 September


Noteworthy events:
63% of all locales shipped signed off updates of Firefox 41 on desktop. Congratulations to everyone who signed off and shipped this last cycle! Sadly, this is a 12% decrease in locale coverage between Firefox 40 and Firefox 41.
74% of all locales shipped signed off updates of Fennec 41 on Android. Congratulations to everyone who signed off and shipped this last cycle! Sadly, this is a 4% decrease in locale coverage between Fennec 40 and Fennec 41.
– Please congratulate the Croatian team on launching their first localization of Firefox for Android with version 41!
– We’re also looking forward to seeing the Purépecha, Kaqchikel, and Lao localization teams launch their first Mozilla localizations in Firefox for Android soon.

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 Balkans Meet-up



Bucharest, Romania was the excellent host of the 5th Mozilla Balkans Community Meet-up. The 2-day workshop took place at the end of May in a similar form as previous Balkans events that were kick-started back in 2010.


The aim of these gatherings is to enable Mozilla communities in the Balkans to share and learn from each other’s experience working on the Mozilla Project, improve collaboration in the future, and work on specific tasks.

Having attended all but one Mozilla Balkans meeting, I feel confident in congratulating Ioana Chiorean for a brilliant job she did working on her specific task – organizing the whole thing. Everything from transportation, accommodation and venue to the drinks out in the open during the Eurovision Song Contest was flawless. Mersi, Ioana!

Ioana - always in action

Ioana was always in action.

Invited were lead contributors from 8 Balkans communities: Albanian, Bulgarian, Croatian, Greek, Macedonian, Romanian, Serbian, and Slovenian. Members of Mozilla staff from 4 different functional areas were also present: Participation Team, Quality Assurance, Support, and Localization.

One of the 5 goals of the Mozilla Balkans community reads Ensure that Firefox and Thunderbird are localized into every Balkan language. While the Thunderbird part may sound slightly outdated as the goal, it clearly shows how important Localization is in this part of the World. So Pike, Flod and I basically went to Bucharest to see how we’re fulfilling this goal.

It doesn't look like Gašper is listening to Pike.

L10n discussion.

We talked to each L10n team attending the meet-up separately to hear their feedback on our tools and translation workflows. One of the questions raised was why do we have so many tools. Well, this problem is now solved. :-) We also provided some ideas on how to plan upcoming work regarding product roadmaps and schedules and recruit new community members.

I found discussions with localizers, both formal and informal, very valuable for the feedback on work I’m personally engaged with. I hope other participants agree with me that such events not only answer questions, but also make us more motivated.

Here’s to the next Balkans Meet-up!

The group photo in brand new Balkans T-Shirts!

And, of course, the brand new Mozilla Balkans T-Shirts (hello, Flod)!

Firefox l10n report (Aurora 42)

Jeff Beatty


Hello localizers!

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

This cycle (Fx42) — 11 August – 21 September


Key dates:
– Beta (41) sign-offs for new locales must be completed by 2 September.
– Beta (41) sign offs for already shipping locales must be completed before 9 September.
– Aurora (42) sign offs must be completed before 21 September.

– Approximately 394 new string changes landed in Firefox Aurora desktop and 87 for Fennec Aurora exclusively (unshared).
– 100% of the Firefox desktop string changes are showing in the dashboard as new strings/files that need translation, however, many of these strings are part of devtools refactoring (i.e., they were moved from one location to another, in several cases existing strings got new IDs). For those of you working directly with HG, this will be helpful to understand these changes: . For those of you working on Pootle, the system’s translation memory should automatically provide you with translation matches as suggestions from when you translated these strings previously.

  • ~30% of the new strings in devtools.
  • ~27% are in dom.
  • ~16% are related to privacy settings, tracking protection, and private browsing.
  • ~7% are related to password management.
  • ~6% are related to Firefox Hello (loop) and Firefox Accounts.
  • Finally, about 4% are related to WebRTC.

Please see for more info.

– 68% of the Fennec strings changes are new strings/files that need translation.

  • 15% of those new strings are related to performing remote operations in the browser.
  • ~17% of them  are related to login prompts and credential management.
  • ~40% of them are related to private browsing, tracing protection, and privacy settings.
  • Finally, 13% of them are related to mixed content and tabbed browsing.

Please see for more information.

Last cycle — 29 June – 10 August


Noteworthy events:
75% of all locales shipped Firefox 40 on desktop updates on time. Congratulations to everyone who signed off and shipped this last cycle! This is a 7% increase in locale coverage between Firefox 39 and Firefox 40! Congratulations!
78% of all locales shipped Fennec 40 on time. Congratulations to everyone who signed off and shipped this last cycle! This is a 1% increase in locale coverage between Fennec 39 and Fennec 40. Congratulations!
– We had the single largest number of locales ever to sign off on the launch of a Mozilla product today with Firefox for iOS. iOS users will be able to access Firefox in up to 36 languages in the first release! This is a major accomplishment for the Mozilla localization communities! Please take a moment to celebrate a job extremely well done.
– We’re looking forward to congratulating the Croatian team next cycle for launching their first localization of Firefox for Android. We’re also looking forward to seeing the Purépecha and Kaqchikel localization teams launch their first Mozilla localizations in Firefox for Android soon.

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 Baltic l10n Meet-up



At the beginning of June, together with my colleague Axel, we headed to Vilnius (Lithuania) for the Baltic l10n meet-up. The plan for the week-end was to meet some of our localization teams in the Baltic and East Europe area, get them up to speed on Mozilla’s mission and future, and discuss each team’s status and needs.

Vilnius - June 2015

The event was hosted at the Mathematics and Informatics faculty of Vilnius University, and it wouldn’t have been possible without the help and logistical support of Rimas Kudelis, historical maintainer of the Lithuanian localization, and host extraordinaire.

We managed to gather localizers for Estonian, Latvian, Lithuanian, Polish, and Ukrainian, in the same room, all together possessing a very diverse mix of experience. Localization is one of the groups at Mozilla with the highest number of “old guard” contributors, but we had a lot of people who only recently joined the project, with involvement ranging from 1 month to 1 year. As far as I know, this meet-up also holds the record for our youngest l10n contributor (Jānis, Latvian).

Given the number of “new-guard” contributors, we started the first day with an introduction on Mozilla’s mission, largely based on the presentation that Mitchell gave in Portland at the end of 2014. Then moved to other themes like Firefox 38.0.5, plans for the next southern-spring release, and the decision making process at Mozilla. On the second morning we focused on tools and Firefox OS, leaving the afternoon – like the day before – to each team to catch up with actual localization work.

During the various discussions, one interesting idea came from the Latvian team: Google is doing an incredible job with doodles, celebrating local relevant dates, historical figures, etc. Can we use home page snippets in a similar way to promote localization? For example: create a snippet with a national Latvian theme, promoting localization and targeting en-US users in Latvia. That, together with the idea of promoting alternative downloads emerged at the Celtic meet-up, would greatly improve the visibility of some of our localizations.

We also need to figure out the secret behind the growth of the Lithuanian team: it moved from being a one-man band for several years, to having several active contributors in just a couple of years.

Here’s a brief list of other topics that, I believe, require more thinking and follow-ups:

  • Decision making: sometimes localization teams feel excluded from discussions. Mozilla needs to improve the way it communicates key decisions, not just to the general public, but more importantly to the community of core contributors.
  • How can we improve the interaction with Reps, and make localization as appealing as other initiatives (maker parties, app development, etc.)?
  • l10n mailing lists: can we improve the signal to noise ratio?
  • l10n testing: how do we get access to platforms that are not available in a localization team (e.g. Windows or OS X machines, iOS devices, etc.)?

Note to self: make always sure that someone is covering the event with photos, and organize the group shot at the end of the first day. Also write these posts earlier, before memories get foggy 😉

I’d also like to thank publicly our colleague Jeff Beatty: it’s so easy to travel around the world without worries only because there’s someone behind you who’s taking care of organizing these trips down to the smallest detail, and managing the immense amount of paperwork and emails. Thanks Jeff, both from your colleagues and all the localizers who, thanks to your work, are able to enjoy these events to the fullest.