Initially, I sketched out what I thought would be valuable information for the report, ran it by the l10n-drivers, and sent it to the metrics team to start implementation.  In my opinion, an effective report provides both download and active daily user information to our localizers about their locales AND the geos in which their locales are being used.  Let’s review the contents for those who might need a guide.  Feel free to reference the attached screen shots as you read.

Locale-specific information

We are presenting both the download and active daily user (ADU) information (usages statistics and pie charts) for versions of Firefox.  ADUs are based on the blocklist pings we track.  (More on blocklist can be found at Morgamic’s post.)

Geographic-specific information

Each report will show both the download and blocklist for the top five locales inside a country where the localizer’s translated Firefox is most prominently used.  In many cases, this is easy to map.  Locale code “fr” is probably most prominently used in France.  “de” in Germany.  “es-ES” in Spain.  In some cases, we’ll have to make guesses, like for our Kurdish localizers.   Finally, we will provide a list of the top ten countries (by average blocklist pings) where the localizer’s Firefox is being used.

For the first time, our community of l10n volunteers will have a more comprehensive set of data points to help measure the progress and spread of their work.  By providing both locale and geographic information, these reports illustrate the impact that each localization team is providing.

Below are two images of a sample two page report.

and

ShareThis

“In Mozcamp i said, mozilla is no helping just to translate firefox to mayan, mozilla is helping to rescue and make strong the mayan language. Well, i’ll send it and we’ll be in contact.” [sic]

Aw, shucks.  That just makes me happy.

Maybe I have delusions of grandeur as I sit here and sip my Kool-Aid, but I think there is something critical to language preservation happening in the Mozilla localization project for cultural anthropologist and linguists to study.  I’ve discussed this topic with other Mozillans who are interested like Tiffney Mortensen, Chofmann, Staś, John Lilly, Søren Skrøder (Mozilla Denmark), and Kadir Topal (Mozilla Germany).  Every time we ship a new version, even for some of the most niche locales, Mozilla helps just a little bit to preserve the culture of language and communication.  Imagine how unique an experience it becomes for a total newcomer to browse the web with an application whose user interface is both translated and customized for local use.  That can be very powerful and is why we want Mozilla locale count to continue to grow.

To see a little more about what our Mayan friends are doing, check out these links:

• Mayan Firefox language pack
• Screen shot of Mayan Firefox
• Mozilla México en Mérida, Yucatán
• Local press

Do you know of a new localization effort?  I will pay chocolate dipped cake donuts for every referral that becomes a localization.  

ShareThis

Something had to change, but to rectify that problem was a daunting task.  Not only were documents outdated or obsolete, but also they were scattered through the Mozilla Wiki (wikimo) and the Mozilla Developer Center (MDC) like wet leaves across a yard, over into flowerbeds and onto the driveway.

Staś (and the l10n team, but primarily Staś) took up the goal of overhauling Mozilla’s l10n documentation.  One result of a lot of work and many meetings was a Delicious page that we created and titled “Mozdocs“.  If you’ve clicked through on that link, you’ll see our attempt to bookmark and tag *every document written* about Mozilla localization.  This became our base for updating all of our documentation.

The Mozdocs Site

Staś determined that the best way to work was to create an inventory of what we had, categorize that, and then begin work.  And so, we began by finding pages in our documentation and adding them to the Mozdocs page.  We then tagged each page we found with something that described it.

Tagging pages became critical in our ability to work on these docs.  Staś created a set of meta tags that tell us some information about the state of the page.  Namely, does it need to be updated, is it obsolete, does it need to be fixed, should it be deleted, and more.  We also have “location” tags that tell us where we found the document (i.e. my blog, Axel’s blog, Mozilla Wiki, etc.).  Lastly, we have general purpose tags that describe the document.

If you’re interested, Mozdocs could be a very helpful page for you to get a sense of what is in the Mozilla L10n inventory of docs.

New documents, New Naming Guidelines

As foreman of the cleanup crew, Staś also determined that we needed to separate our documents properly.  MDC would serve as the place for docs that describe how to develop and localize and can be abstrated from the Mozilla process.  The Mozilla Wiki would serve as the spot for anything specific to the Mozilla Project’s localization process.

Get that?  MDC = how to/abstract from Mozilla; Wikimo = Mozilla process.

As we created and edited documents, we made sure that they were placed on the proper platform.  Furthermore, we started to rename documents using new “Naming Guidelines“.  If you plan to create a new localization document on the Mozilla Wiki or MDC, we are asking that you use the following (Below is one massive hyperlink to the Naming Guidelines from the previous sentence):

1. Always use the L10n: namespace (wikimo only)
   • Bad: Firefox_productization_guidelines
   • Bad: L10n_Firefox_Productization
   • Good: L10n:Firefox/Productization
2. For hierarchies, use /, not :. This will create breadcrumbs automatically.
   • Bad: L10n:Firefox:Productization
   • Good: L10n:Firefox/Productization
3. Prefer hierarchies than longer names if you need to disambiguate.
   • Bad: L10n:Firefox_Productization
   • Good: L10n:Firefox/Productization
4. If not ambiguous, simplify.
   • Bad: L10n:Product/Firefox/Namoroka
   • Good: L10n:Namoroka
   • Good: L10n:Firefox/Productization and L10n:Mobile/Productization are OK, because L10n:Productization is a more general document.
5. Don’t repeat yourself:
   • Bad: L10n:Firefox/Firefox_Productization
   • Good: L10n:Firefox/Productization
6. Add localization-related tags (on MDC) or categories (on wikimo)
   • On wikimo, use [[Category:L10n]] anywhere in the contents of the page.

Our hope is that all new pages that deal with Localization will follow these naming guidelines.

And now, your turn…

As I mentioned, if you’re interested in scanning the inventory of documents, take a look at Mozdocs and the tags we have created.  This could be a very helpful page for you to get a sense of what is in the Mozilla L10n inventory of docs.

Also, if you are finding new documents, can you please tell us and we’ll tag them on the Delicious site?  Staś is the module owner of this site and we are accepting any “patches” to it.  So, if you want to add something, just let us know and we will make the change.

ShareThis

ShareThis

Last quarter, the l10n-drivers set out to document the steps necessary to make a web site or web application localizable (i.e. designing a project so it can be translated and localized).  All too often, we found ourselves providing feedback on projects that had begun with the intention to reach a global audience, but had not been designed to scale at the intended level.

To illustrate our point, we decided to choose a real life example that we could go through with a team of project managers to document the steps necessary to make a project localizable.  What we needed was a pilot project that had launched quickly to test a concept and see if the idea had enough global appeal that it would require localization.  We chose Get Personas as the test case because it fit our criteria perfectly.  With this project, Mozilla Labs had a site that had launched to prove its concept.  Mozilla Labs often moves quickly and may not have the time or resources to map out just what of its many projects might take off since some of them may not.  In this case, Personas quickly appeared to have global appeal and a need for l10n, but it contained project design flaws that did not have localization in mind from the beginning.

After working for the entire quarter with Mozilla’s Ryan Doherty, who was charged with making the site localizable, Staś Małolepszy, with Pascal Chevrel’s guidance and some from me, compiled all that we learned into several documents now hosted on the Mozilla wiki and on the Mozilla Development Center.  Our intended audience for these documents is marketing and web dev folks.

If you’ve ever wondered what it takes to make a website localizable so it can scale to a global audience, please take a look at this wiki page and its links to other important documentation.

We’ll walk through the piece of this wiki page in more detail in a few forthcoming posts.

ShareThis

Got a presentation or topic you want to discuss?  Email me or comment or this blog and we’ll see how to get it in a slot.  I intentionally left some open blocks so localizers can attend other non-l10n talks of interest.   See you in Prague next week.

ShareThis

“This causes the comment to become irrelevant to the text it references.  Additionally, if someone then fixes the localization note, localizers won’t be notified on this change, and the comment does not get changed in our translations…As some of us are actually reading such comments before translating, it is important to get it 100% accurate.”

Here is an example that Tomer provides.

<!– LOCALIZATION NOTE (bookmarksSidebarGtkCmd.commandkey): This command
-  key should not contain the letters A-F, since these are reserved
-  shortcut keys on Linux. –>
<!ENTITY bookmarksGtkCmd.commandkey “o”>

You can see that example in our code on MXR here:  http://mxr.mozilla.org/mozilla1.9.2/source/browser/locales/en-US/chrome/browser/browser.dtd#110

For those readers who may not be seeing what is happening here, notice that the <!– LOCALIZATION NOTE –> is referencing “bookmarksSidebarGtkCmd.commandkey“, but the !ENTITY variable name is actually “bookmarksGtkCmd.commandkey“.

That mismatch in the entity names has made that localization note untrackable by any locaization tools.  Unfortunately, localization tools will not understand which comment belongs to bookmarksGtkCmd.commandkey.  Furthermore, localizers who use these notes for translations will have to make the educated guess where the comment is pointing.  If the note gets updated in the future, it’s likely that localizers will miss it.

Tomer suggested writing a script to look for these mismatches.  In the very least, I am hoping this post will spread the awareness to developers to remember to do this.  A quick request from l10n community: please maintain localization notes if entities get changed.

ShareThis

• Population is 92 million, online population is between 20-24 million
• English is one of the official languages of the Philippines.  Tagalog is spoken by roughly 22 million people in and around Manila.  Cebuano is another language spoken by nearly 20 million Filipinos south of the Luzon region (where Manila is located).
• Depending on what factor we use as a multiplier for our blocklist/AUS ping data, we can estimate that between 3 and 6 million Filipinos are using Firefox.  That is a rough guess, but it places Firefox market share at a low-end of 12.5% and a high-end of 30%
• Most people we spoke to browse the Web in English (Firefox US version), but some did suggest that a local version would have appeal.
• Even further debate arose on whether a Tagalog version would have traction, with an audience of bloggers at Wordcamp responding collectively that it might not.

That latter point does not rule out Mozilla shipping a local version of Firefox.  But, like every other localization, if we were to ship something localized to the Philippines, it will be because a local community member(s) responds to my call to action and decides to help us complete the body of work.

Obviously, Mozilla Firefox is taking off in the the Philippines, so I wouldn’t be surprised to see if the nascent community stepped forward with an offer to localize Firefox.

Finally, take a look at some stats about Firefox in the Philippines.  (All numbers are based on our blocklist data.)

Growth of blocklist pings over one year

The Philippines is #4 on the list

ShareThis

1. To gain further insight into the landscapeof the Web and Internet in the Philippines;
2. To assess whether or not a localized version is something our community here mightpursue;
3. To meet our community of campus reps and others.

It’s been a steamy (as in the humidity), but amazingly kind reception here and we booked our schedules full with meetings and events. That’s all Gen’s amazing work.

As for my WordCamp chat, here is my presentation. I started by taking the audience through our open web demos (video, canvas, svg, css, js etc. thank you Paul Rouget…), and then honed in on describing our Mozilla community, using localization as an example of how we are a global community of passionate contributors working to promote Mozilla’s mission.

My call to action was two-fold: the blogging community can help promote the Open Web through their blogs, AND, if people feel empowered to do so, let’s start a localization for Filipino users.

Feedback from these local bloggers was energetic, questions were poignant, and the message was embraced. My prediction, a Mozilla community here is going to take off if we continue to nurture, empower, and participate.

I am trying to embed the presentation here, based on some code that Gen shared with me, but it looks like it is not working.

ShareThis

However, as we ramp up our efforts to localize Firefox 3.6, and a mobile Firefox, we have been reaching out to our “mn” community leader, Natsagdorj (Nagi) Shagdar, but have had no response to the emails we have sent.  I guess it’s an inevitability to have some turnover when a 100% volunteer community rallies together to ship Firefox in over 70 languages.  Building sustainable communities is critical to our ongoing success and something we take very seriously.

Therefore, this is an open blog post to reconnect with our Mongolian team in order to make sure everything is OK and receive a status update on the work/team going forward.  It would be terrific to receive an email from Nagi or others to let me know how to proceed with work on the mn locale.

This post serves a secondary purpose because we also would like to invite any others interested in joining the Mozilla Mongolian community to contact us.  We are looking for community members to help take up some of the localization effort so we don’t lose all that we have accomplished with the mn version.  Plus, we don’t want to let down thousands of our Mongolian users who will be looking for the latest and greatest when Firefox 3.6 comes out.

If you have interest in joining the community or know of anyone who might help in some capacity (even with simple referrals), then contact me through the comment section of this blog.  We have a robust set of community members and tools that makes localization easy and fun.

As a matter of fact, we are welcoming all newcomers, so just ping me.  Thanks, everyone!

ShareThis