L10n:Localizability/Web: Difference between revisions

L10n:Localizability/Web (view source)

Revision as of 23:57, 21 May 2009

790 bytes removed , 21 May 2009

→‎Topics for consideration when asking for project localization

Sbindernagel@mozilla.com

1,068

edits

@@ Line 34: / Line 34: @@
 == Topics for consideration when asking for project localization ==
-For each project that requires web development and eventual localization, the following points should be considered:
+For each project that requires web development and eventual localization, you should consider the following points:
+*  At Mozilla, translation by localizers is 100% volunteer-driven
+**  What happens if a localization team does not have time to take on your request?  Or, simply says, "No"?
 *  Images should not contain content
-*  At Mozilla, translation by localizers is 100% volunteer-driven
+*  Depending on the project, l10n-drivers likes to have anywhere from 6 weeks to an entire quarter of planning time.
-*#  What happens if a localization team does not have time to take on your request?  Or, simply says, no?
+*  Ask [mailto:sethb@mozilla.com sethb] if you want to know the current localization work load.
-*  What is the time line for your work?  What is the launch date?
-**Depending on the project, l10n-drivers likes to have anywhere from 6 weeks to an entire quarter of forewarning.
-*  What is the current l10n workload?  Just ask [mailto:sethb@mozilla.com sethb].
-*  Web localization requires a string- and code-freeze so localizers can update the work.  What does a "code freeze" really mean?
-*#  Strings cannot change
-*#  Expect to stop modifying content on your site
-*#  Your website will become frozen
-*#  l10n and QA will need to verify that the site is localizable
 *  Beware of localization burnout
-*#  Updating content is an often laborious task.  How "evergreen" is the content on your site?  How often do you plan to change it?
+**  Updating content is an often laborious task.  How "evergreen" is the content on your site?  How often do you plan to change it?
-*  Will your project have a release cycle?
+*  Will your project have a life-cycle?
-*#  If the lifespan of the project is short, then, ideally, the localization requirements should not be complex.
+**  Short project life-cycle: localization requirements should not be complex
-*#  If the lifespan is long, we should use techniques to make updating the site much easier
+**  Long project life-cycle: use techniques to make updating the site much easier
-*  Consider the prioritization of other projects
-*#  What else is in the l10n queue?
-*#  What sites are mandatory?  Tier 1, tier 2, tier 3?  All locales are typically offered the opportunity.
-*  What content is actually priority?
-*#  SUMO lists the top ten articles where localizers should start.  Does your project have the ability to categorize information into various hierarchies?
 == Download Day, a case-study ==