1,068
edits
L10n:Localizability/Web: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
This document describes the steps you need to consider and take to localize your project. 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. | This document describes the steps you need to consider and take to localize your project. 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. | ||
== Localization checklist == | |||
* Present a clear time line to l10n-drivers so we can manage the amount of work needing localization | |||
* Create a release schedule for your site so you can change content if needed | |||
:# AMO has a three-week release cycle and l10n changes happen every so often | |||
* Create templates that separate logic from localizable content | |||
:# PHP allows you to separate logic of application from localizable content | |||
:# [http://hg.mozilla.org/labs/personas/file/9467ef3c369c/server/faq.php This example] co-mingles the PHP code with localizable content. If a localizer happens to change this logic, it will break the entire site | |||
* Images should not contain content | |||
* Set up a version control system, preferably SVN, which our localizers know | |||
* Join the [http://groups.google.com/group/mozilla.dev.l10n.web/topics?lnk=srg Mozilla.dev.l10n.web Google Group] | |||
* Chat with web-dev and QA to set up a staging server | |||
* Notify QA lead that l10n is a requirment | |||
* Make your project's file type decision | |||
*# html | |||
*# .lang | |||
*# Gettext | |||
* Verify all copy to confirm that strings you are using will not change after localizers start working | |||
*# Localizers will not start working until there is final sign off | |||
== Topics for consideration when asking for project localization == | == Topics for consideration when asking for project localization == | ||
| Line 25: | Line 45: | ||
* What content is actually priority? | * 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? | *# SUMO lists the top ten articles where localizers should start. Does your project have the ability to categorize information into various hierarchies? | ||
== Technical L10n Design choices == | == Technical L10n Design choices == | ||