Mozilla LATAM L10n & QA Hackathon 2015

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)

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.

Features:
– 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 https://www-dev.allizom.org/en-US/firefox/43.0a2/auroranotes/ 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 – https://bugzilla.mozilla.org/show_bug.cgi?id=1207108 .Please see https://www-dev.allizom.org/en-US/firefox/android/43.0a2/auroranotes/ 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.

800px-MozBalkans_Logo_lung

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)

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.

Features:
– 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: https://hg.mozilla.org/mozilla-central/rev/3301c85aa671 . 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 https://www.mozilla.org/en-US/firefox/42.0a2/auroranotes/ 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 https://www.mozilla.org/en-US/firefox/android/42.0a2/auroranotes/ 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.

Mozilla Nordic L10n Hackathon 2015

At the end of April 2015, Axel Hecht, Matjaž Horvat, George Roter, and I took a trip to Stockholm to organize a l10n hackathon for the Nordic l10n teams. The last time we did something like this was in 2013. Essentially, Brian King, Axel, and I organized a central Nordic hackathon in Copenhagen, then we hopped in a car and drove from there to Gothenburg, Oslo, and Stockholm, organizing MozCafes all along the way to learn more about the Nordic community. On my way to meet with Brian and Axel in Copenhagen, I also stopped into Reykjavík for Iceland’s first MozCafe.

Since that experience, members from various Nordic communities expressed a lot of interest in holding another Nordic community meetup targeted at localization within the region. We were more than happy to help! Not only were we happy to help, but staff from Wikimedia Sverige were very happy to allow us to use their office space for the event. They shared with us how their community is growing and were excited to be able to collaborate with Mozilla for this event.

Continue reading …

Firefox L10n Report (Aurora 41)

Hello localizers!

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

This cycle (Fx41) — 29 June – 10 August

 

Key dates:
– Beta (40) sign-offs for new locales must be completed by 22 July.
– Beta (40) sign offs for already shipping locales must be completed before 29 July.
– Aurora (41) sign offs must be completed before 10 August.
– The next major Firefox seasonal release is Firefox 42, which will be available for l10n on 10 August. I’ll be sending more information about this in the coming weeks.

Features:
– Approximately 199 new string changes landed in Firefox Aurora desktop and 79 for Fennec Aurora exclusively (unshared).
– 63% of the Firefox desktop string changes are new strings/files that need translation (125). 53% of those new desktop strings are in devtools. 14% are related to Telemetry services. 10% are related to add-ons management and 5% are related to Pocket. Please see https://www.mozilla.org/en-US/firefox/41.0a2/auroranotes/ for more info.
– 66% of the Fennec strings changes are new strings/files that need translation. ~24% of those are related to unsigned addon management. ~17% of those new strings are related to private browsing. ~23% of those new strings are related to various prefs (data privacy, QR code reading, etc.). Please see https://www.mozilla.org/en-US/firefox/android/41.0a2/auroranotes/ for more information.

Notes:
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. Users for some Firefox and Fennec locales have not received a proper updated localization in the last 30 weeks to a year. If you belong to one of these locales, I’ll be reaching out to you this cycle to discuss the future of your locale as an official localization.

Last cycle — 11 May – 29 June
   

  Noteworthy events:
69% of all locales shipped Firefox 39 on desktop updates on time. Congratulations to everyone who signed off and shipped this last cycle! Sadly, this is a 13% decrease in locale coverage between Firefox 38 and Firefox 39.
77% of all locales shipped Fennec 39 on time. Congratulations to everyone who signed off and shipped this last cycle! Sadly, this is a 10% decrease in locale coverage between Fennec 38 and Fennec 39.

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 (Aurora 40)

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.

Features:
– 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 https://wiki.mozilla.org/Features/Release_Tracking#Likely_in_Firefox_40 for more info.
– 2 devtools files, (gcli.properties and gclicommands.properties) 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.

Notes:
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

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 mozilla.org 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.

Conclusions

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: