L10n:Localizability/Web: Difference between revisions

Jump to navigation Jump to search
Line 31: Line 31:
#*  Functionality
#*  Functionality
#*  Locales affected
#*  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.
#**  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.
#**  What happens if a localization team does not have time to take on your request or simply says, "No"?
#**  Consider as well what happens if a localization team does not have time to take on your request or simply says, "No."
#*  What is the budget and resources available to allocate to this project?
#*  Available budget and resources
#*  Project's '''expected life-cycle''' (one-time/short/long?)
#*  Expected life-cycle (one-time/short/long?)
#**  Short project life-cycle: localization requirements should not be complex
#**  For projects with short life-cycles:  
#**  Long project life-cycle: use techniques to make updating the site much easier
#*** Localization requirements should be simple.
#*** Updating content is an often laborious task. Beware of localization burnout.
#**  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 "evergreen" is the content on your site?   
#*** How often do you plan to change it?
#*** How often do you plan to change it?
Account confirmers, canmove, Confirmed users
2,357

edits

Navigation menu