Account confirmers, canmove, Confirmed users
2,357
edits
L10n:Localizing Projects and Content: Difference between revisions
Jump to navigation
Jump to search
→The considerations
| Line 13: | Line 13: | ||
* It's been our experience that highly visible, critical pages, like the "What's new" page, can require '''2-4 weeks for 40 locales to localize'''. If your project has less exposure, please allow for more time. | * It's been our experience that highly visible, critical pages, like the "What's new" page, can require '''2-4 weeks for 40 locales to localize'''. If your project has less exposure, please allow for more time. | ||
* Be sure that you are linking to the appropriate locale sites for your project (e.g., Mozilla Hispano's twitter account instead of their PR site). | * Be sure that you are linking to the appropriate locale sites for your project (e.g., Mozilla Hispano's twitter account instead of their PR site). | ||
* Get L10n involved as early as possible. This will help us to collaborate with you on setting manageable release dates for your project. | |||
* It is important to provide us with as much information as possible in your project's form, even if the info contains mostly rough estimates. L10n turnaround and planning are largely based on three things: | |||
*# The infrastructure required to leverage the L10n teams and implement their work. | |||
*# The number of final source strings. | |||
*# The number of target locales for your project. | |||
=The process= | =The process= | ||