L10n:Localizability/Web

At Mozilla, translation by localizers is 100% volunteer-driven. This document describes the steps you need to consider and take to localize your web project while respecting localizers' time and work. After reading this document, you should be able to construct a good localization plan that acknowledges a process for all to follow and the technical choices you need to make before starting.

The process explained from A to Z. After Web Dev has approved the development of your project, immediately contact l10n-drivers to discuss your localization strategy for the order of events described here.

Checklist

After Web Dev has approved the development of your project, immediately contact l10n-drivers to discuss your localization strategy for the following order of events:

Create a clear timeline for the l10n-drivers to manage the workflow to localizers.

Depending on the project's scope, the l10n-drivers need anywhere from 6 weeks to a quarter of planning time.

Consult with Pike to know the current localization workload and where your project will fit within it.

Keep in mind, it's been our experience that highly visible, critical pages, like the "What's new" page, can require 3 weeks for 40 locales to localize. If your project has less exposure, please allow for more time.

Prepare a project scope outline that describes the points below:

Length of content (in number of strings and words)

Functionality

Locales affected

Keep in mind that our localizer community is overall very active and enthusiastic. However, other locales (not from the "affected" list) may ask why they weren't targeted for your project and if they can participate. Be prepared to have an answer for them.

Consider as well what happens if a localization team does not have time to take on your request or simply says, "No."

Available budget and resources

Expected life-cycle (one-time/short/long?)

For projects with short life-cycles:

Localization requirements should be simple.

For projects with long life-cycles:

Use techniques to make updating the site much easier.

Updating content is a laborious task. Beware of localization burnout.

How "evergreen" is the content on your site?

How often do you plan to change it?

Create a release schedule for the project.

Prioritize your content (i.e., What pages are mandatory for which locales?). Consider different requirement for different tiers.