L10n:Localizing Projects and Content: Difference between revisions

L10n:Localizing Projects and Content (view source)

71 bytes added , 4 May 2012

Account confirmers, canmove, Confirmed users

2,357

edits

@@ Line 33: / Line 33: @@
 * Our volunteer localization community is overall very active and enthusiastic. However, non-target locales may ask why they weren't targeted for your project and may request to participate. Should that be the case, be prepared to have an answer for them.
 * Have a plan in mind if a localization team does not have time to take on your request or simply says, "No."
-* Depending on the project's scope, the l10n-drivers will need anywhere from '''6 weeks to a quarter''' of planning time.
+* Depending on the project's scope and classification, the l10n-drivers will need anywhere from '''6 weeks to a quarter for products''' and '''1-3 weeks for web projects''' of planning time.
 * Consult with [mailto:l10n@mozilla.com Pike] to know the current localization workload and where your project could fit within it.
-* 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.
+* 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).