Today we’ve launched a new homepage on l10n.mozilla.org, and a new sandstone theme.
The l10n site now integrates better with the rest of the mozilla websites, and the homepage is more engaging.
Today we’ve launched a new homepage on l10n.mozilla.org, and a new sandstone theme.
The l10n site now integrates better with the rest of the mozilla websites, and the homepage is more engaging.
Language can be very difficult to capture within software localization. Each natural language in the world evolves at its own pace and in its own unique way, creating vibrant and rich means of expression. Sadly, simple static string translation is often ill-equipped to properly accommodate gender, conjugation, plural, or case changes required within the language by changing string variables and other run-time string composition issues. This is why we created L20n.
We’re super happy to announce that we’ve released an amazing tool to help localizers, engineers, and localization tool developers learn and practice L20n themselves! l20n.org contains a real-time text editor that allows you to edit L20n code and visually see how it impacts localization. The real-time editor is part of the “Learn” section of l20n.org dedicated to walk you through what L20n has to offer, feature by feature, and give you a chance to try these features out in real-time.
L20n is a localization framework (comprised of a pseudo-programming language) meant to transfer the ability to localize software using the fullness of any language from the developer to the localizer. L20n empowers localizers to be more independent of source language developers and have more control and flexibility in localizing software according to their native language’s demands.
l20n.org is live and running now! Go give it a try! Not only is it live, but its hosted on github for you to fork and contribute to. Enjoy testing out L20n!
Today we’re very pleased to announce the addition of three new locales to the Firefox Aurora channel: Azerbaijani (az), Burmese (my), and Sakha (sah).
Azerbaijani (az), also known as Azeri, is primarily spoken in Iran, Azerbaijan, Turkey, Armenia, Georgia, Russia, Afghanistan, Iraq, Turkmenistan, and Syria. Ethnologue reports that there are approximately 25,000,000 native Azerbaijani speakers. To help their localization of Firefox move to the Release channel, join the Azerbaijani l10n team.
Burmese (my), also known as Myanmar, is primarily spoken in Burma/Myanmar, Thailand, Malaysia, and Singapore. Ethnoloque reports that there were approximately 32,000,000 native speakers of Burmese in 2000. To help their localization of Firefox move to the Release channel, join the Burmese l10n team.
Congratulations to these teams! We look forward to seeing their hard work on the Release channel soon.
Testing and getting feedback about a localization’s linguistic quality is critical to delivering a browser that will meet users’ needs. We want to attract people in any region to the world’s best browser by making sure that it is the best localized browser available. The language availability and feedback mechanisms vary according to the language’s current status.
At Mozilla, we release Firefox desktop localizations in two ways: through language packs (also known as langpacks) and official builds. Before a language hops on the rapid release train to be distributed as an official build, it is distributed through the Firefox add-ons manager (AMO) as a langpack. L10n teams will update these langpacks as they progress with their l10n efforts. Users in that region (or users whose preferred language is found as a langpack instead of an official build) can download, install, and give feedback on the langpack’s linguistic quality all on the langpack’s AMO page. Here’s a list of all of the current localizations distributed as langpacks.
Official localized builds of Firefox desktop can be found here. These localizations have been technically evaluated by passing rigorous technical reviews. Although they’re on the rapid release train, these Mozilla l10n teams still benefit greatly from receiving feedback from their users. The best way users can provide feedback on a localization’s linguistic quality is to download and install the localized Firefox Aurora build and begin using it as their default browser. As users see translation errors they can log them in Firefox Input, located in the toolbar under Help > Submit Feedback. The Mozilla l10n team responsible for that localization can see their users’ feedback and then make corrections as needed.
Giving feedback is simple and can take as little time as 1-3 minutes to do. If you haven’t already downloaded and installed your language’s Firefox Aurora build or langpack, go for it! Your Mozilla l10n team will be grateful for your help.
We work on two different cycles at Mozilla: a quarterly cycle (this is being posted in Q1) and a six week rapid release cycle. On a quarterly basis, the l10n drivers are responsible for setting goals for the progress they’d like to make on facilitating the localizer’s ability to get involved, the number of new locales we’d like to add to the shipping line-up, and the number of locales who, for one reason or another, have fallen behind and we’d like to help catch up. We attempt to make these goals based on what we assume to know about the l10n teams we’re working with, however, we’ve seen that we often don’t have enough visibility to accurately predict the number of new locales we’ll add to the shipping list or the number of locales that can catch up in a quarter. As you can imagine, these goals aren’t always met by the end of the quarter, largely because they don’t take into account the localizer’s schedule, commitment level, technical experience, or the l10n team’s goals. Well, we’d like to change that
This quarter, along with the l10n team health evaluations, we’d like to encourage all l10n teams to start setting quarterly goals with us and publishing them on their l10n team wiki page under this heading:
===Team quarterly goals===
What type of goals would a l10n team set?
Here’s an example of a l10n team’s quarterly goals:
===Team quarterly goals=== * Sign off on Firefox Beta channel by week 2 of cycle. * Add Fennec to project's list and set goal for which release to ship fully localized Fennec. * Catch up on Firefox Aurora backlog. Be ready to sign off and ship up-to-date localized Firefox desktop at version 22. * Recruit 2 new localizers-in-training. * Make sure all team members have profiles in Mozillians directory and are in both the l10n and l10n:[locale-code] groups.
How will this help my team?
Planning and goal setting not only help you and your team to be more organized and successful, but it allows you to identify areas where new contributors could pick up tasks and join the group. By publishing these goals on your team wiki pages, we’re able to see your efforts and help where we can. Plus, it helps us identify what excites and motivates you as a team. Maybe [insert motivator here, like competition, SWAG, events, accomplishment, etc.] makes your team excited to localize and proud to be part of Mozilla. Your transparent goals will help us to see that and respond in a more personalized manner to your needs.
Need help with goal setting?
If your team needs help setting goals, please reach out. I’m happy to help you focus your efforts and make goals that will improve your efforts. You can also explore the l10n teams directory and see what goals other teams have set and see if they also apply to you.
Everyone is eager to get their hands on Firefox OS in their own language. Since Firefox OS will land in the Brazilian market first, localization is a very high priority. Some l10n teams have already hit the ground running with localizing Gaia. If you take a look at the Firefox OS project on Pootle, you’ll see that Fulah, Scottish Gaelic, and Welsh are already at 100% complete!
Of course we don’t want to stop there; we want everyone to be able to localize Gaia! But where do you start? What tool do you use? How can you test your work in Gaia? Those are the questions that we’re working on answering. In the next few months, we’ll be working on adapting the existing documentation to a wider audience and to our l10n documentation information model. We’ll also be updating it’s content. With this in place, anyone will be able to come in and localize Gaia into their own language!
If you have or are currently localizing Gaia and have already experimented with answering these questions, please get in touch with me (jbeatty [at] mozilla [dot] org) and I’ll be sure to add your experience and learning to the new Gaia l10n documentation.
We’re happy to announce that we’re adding new localizations towith the release of Firefox 16 desktop.
The Kazakh (kk) and Acholi (ach) teams have been working tirelessly to produce the world’s first ever Kazakh and Acholi versions of Firefox desktop for native speakers of the languages wordwide. According to our friends at Wikipedia, there are more than an estimated 10 million native Kazakh speakers and 1.22 native Acholi speakers around the world. Native Kazakh speakers can be found in Kazakhstan, China, Mongolia, Afghanistan, Tajikistan, Turkey, Turkmenistan, Ukraine, Uzbekistan, Russia, and Iran. Native Acholi speakers can be found in Uganda and South Sudan. Thanks to these teams and their efforts, more than 11.22 million native Kazakh and Acholi speakers can now enjoy the option to browse the Web with Firefox 16. The release of a these Firefox desktop localizations brings our total number of regularly shipped languages to 80. Congratulations to the Kazakh and Acholi l10n teams!
We also want to thank all of our l10n teams for their consistent, dedicated efforts to bring the latest innovations of the web to the people of their regions.
See all the different language versions at https://www.mozilla.org/en-US/firefox/all.html.
There are a bunch of new teams out there who have been waiting on progress. Sorry for the wait, but here’s what you’ve been waiting for.
We changed a few things around releasing new localizations. Many things did not change, but I’ll start off with the new.
We’ve redone the process points from review request to being on the rapid release cycle. The purpose was to put less emphasis on the bugs and the technical details, and more emphasis on the l10n dashboard.
We hope to get to a point where localizers are working on the aurora branch on each cycle, and the contribution gets wider testing on beta, and then seamlessly goes to release. We want to have most things lined up before going into aurora and having aurora ready in one 6 week period. Then migrate to beta, get wider testing, and on the same version go to final, if the community review passes.
To do that we did the following:
And again, we put your team page front and center. That’s where you find what’s up to do, in the initial phase and beyond as we move from one cycle to the next.
Things that did not change:
The next batch of localizations we’re taking is going to ride along Firefox 18, coming on to Aurora next week.
Part of a series similar to the Awesome L10n Communities series where individual contributors are spotlighted for their efforts.
Started with Mozilla project: Firefox
Languages: Fulah (Pulaar-Fulfulde), Wolof, Arabic, Soninke, French, English, Spanish, survival Italian
Background: I studied Applied Linguistics, Language Teaching Methodology, Translation and CALL (Computer Assisted Language Learning) at Moray House College in Edinburgh, Scotland.
My team and I have been involved in Fulah translation and localization as well as promoting the language on the Internet (www.pulaagu.com). In 2009, I led the Fulah teams on the 100 locales program and successfully completed the work for locales for Fulah_sn, Fulah_mr, and Fulah_gn. I also created most Fulah terminology for ICT, especially Firefox terminology. Fulah is not a well-resourced language and almost everything had to be created from scratch. But we have implemented a method of creating terminology that respects consistency and coherence.
I started translating Joomla and other open source CMSs. Then I discovered Tuxpaint and started translation with PoEdit. In 2009 I completed the Fulah part of the “locales for 100 African languages” project. I was also involved in translation of Pootle’s basic terminology and Pootle server into Fulah.
Our biggest achievement yet is the localization of Firefox in Fulah which is released this summer (2012).
I have worked extensively on font creation, keyboard layouts creation and I am planning to build a physical “pan-Senegalese/Mauritanian” keyboard usable to type Fulah, Wolof, Soninke, Sereer. I speak, read and write English, French, Fulah (Pulaar-Fulfulde) Mauritanian Arabic, and Wolof. I read and write Spanish, some Italian and Arabic.
I like web and graphics design and when I have time, I write news articles for my website in Fulah (www.pulaagu.com), the first website ever in the Fulah language and the most visited. I use the Internet daily as administrator of two websites and a community blog and my personal blog, all of these dedicated to the Fulah language and culture.
Role in L10n community:
Fulah localisation team lead and major contributor (95% of Firefox). SUMO contributor and KB l10n. Created most of Fulah Internet and IT terminology from scratch.
Projects you’re currently working on:
Firefox, SUMO KB, “50 videos for mastering Firefox in Fulah”, Firefox OS localization (unofficially).
How did you get started with the Mozilla project?
I usually say I have been a localizer ever since because as a kid (from 8/9), I used to translate letters written in French for Fulah speakers who are illiterate. But I started the Firefox project with ANLOC (African Network for Localization). After successfully completing the localization of many other projects like TuxPaint, Abiword, Virtaal and Pootle, Dwayne Bailey from Translate.org.za proposed to localize Firefox. We could not believe it since I have always been a true believer in open source but also a user of Firefox since early releases.
I was not afraid of big projects, so I tried to get a few people from Fulah communities together to start working, but many were either not motivated or have not enough knowledge of IT. Since 95% of IT related terminology had yet to be created, I thought I would start the work and show people that nothing is impossible. It is only when the first early screenshots of the Firefox interface in Fulah were published that many joined. Dwayne created language packs so we could test our Firefox locally, and that has definitely triggered major interest in the Fulah community.
What tips or tricks do you use for overcoming blocks and bugs in your L10n work?
As I mentioned earlier, we had a real chance to have Dwayne Bailey helping out should we have any issues to deal with, and it is Dwayne who runs and manages the Pootle server we are using for the localization work. Pootle has fantastic built-in features for checking errors, bugs and other terminology related issues. With the translation memory, it is a lot easier to manage terminology consistency and Pootle does that really well.
So I would say that Dwayne’s help has been crucial and I learned a lot from him and also Friedel Wolff, one of the authors of Virtaal.
How do you help your team find new L10n contributors?
Fulah has a huge contributor potential because we are very “language conscious” people. Many Fulah people living in those twenty countries have strong feelings about being a Fulah, and the language is what makes us feel we belong the same people, although we are nationals of many countries.
Unfortunately, the Internet is the only way we can communicate and that is not yet considered as “real.” You have to meet people in person, convince them to work as volunteers, then train them to use all these tools. Recruiting is quite easy, but most who are really fluent in Fulah are not necessarily motivated to spend hours working for free! Or they just cannot access the Internet at home or maybe just don’t have a personal computer.
I am planning a number of l10n workshops in France, Senegal, Mali and Mauritania to trains SUMO volunteers. Most of the potential and actual contributors live in Africa. So it is not very efficient to just use email as it is too “unreal” and distant to get people to really feel they are involved. I hope Mozilla will help achieve this. Basically, contributors are there but you have to reach out to them in a more humanized manner to motivate them even more.
What’s your philosophy/method on mentoring new contributors?
Usually those who are involved already know me from other contributions to Fulah digitization, codification and promotion. So it is usually an honor for them when I contact them to ask them to work for Firefox. But again in my culture, you really need to meet people to establish a real contact and show them you are there to help, train, and support.
But I must say it is very hard to get people to work for free when they are struggling to make ends meet. So [I try] to have a personal relationship with them, [which usually leads to us] becoming friends. I call them quite often and not only to talk about contributing. That is the best way of having them around even when they are not really contributing.
But the most efficient way of mentoring them is to show them that they can do things and that they should not be afraid of all these tech terms they are not very familiar with. They can call me, invite me to talk on Skype, or post on my Facebook wall.
Since people are working as volunteers, you need to constantly make them feel they are actually making a difference no matter how much they contribute.
If you could identify several best practices that have helped you to become a successful Mozilla localizer, what would they be?
I think my personal motivation helped me a good deal in going ahead with the Mozilla project. So to keep motivation at a satisfactory level, it is important to adopt a effective strategy to make the work less tedious. As for Fulah, I could certainly not have been so successful [had I] not used Pootle server and Virtaal (translation editor).
Since Virtaal is an offline editor, I used it for translating .po files then checking errors offline before uploading to the server (Pootle). Then we can use Pootle to make the usual checks. So Pootle and Virtaal are really efficient tools that allow you to adopt a workflow that makes the task less scary.
As a team lead, I worked very hard to complete the biggest files to motivate others. So being the biggest contributor is also a good way of boosting others’ motivation.
Finally, in any type of work, being organized is a key strategy. When you start a huge project like Firefox l10n, you live in doubt whether you are fit for the job or not. You think you will never finish and soon wonder if it is worth carrying on something that will never end. What I believe is you have to fit the project into your everyday life.
These are just what worked for me and I hope it will help others to start, complete or update their localization. And I one day, I got this message from Milos Dinic:
I just want to say we’re happy how things are evolving and that Fulah is one of the very few locales that we’re releasing in one train (started in aurora with Firefox 14, moved to beta in Firefox 14, and releasing in Firefox 14).
So, yes, we’re releasing Firefox in Fulah in this cycle, and I’ll close the tracking bug past the release (July 14).
Keep up the good work!
These are the most beautiful words I have heard recently and I was speechless when I read that jaw-dropping news that drove me to tears.
What are you most looking forward to accomplishing this year?
Since we have completed Firefox with such efficiency, my objective this year and in 2013 is to hold talks and organize workshops in Africa to recruit dozens of contributors and spread the word about Firefox and Mozilla products.
I’d like to do so by attending major cultural events like the Blues du Fleuve festival which is organized by Senegalese world music superstar Baaba Maal, humanitarian activist and Global Ambassador for OXFAM (www.baabamaal.tv) or the Water Festival in the same region.
What projects are you most looking forward to working on this year?
Good question! Firefox OS!! Localization for Firefox OS is something that I am ready for and jsut too excited about. You know for a people that are divided into 20 countries, life is the web and the web in African is mobile, and mobile it will remain. So Mozilla you know what’s next now…
Five things you may not know about me: