1,068
edits
L10n:Localizability/Web: Difference between revisions
Jump to navigation
Jump to search
→Localization checklist
No edit summary |
|||
| Line 3: | Line 3: | ||
== Localization checklist == | == Localization checklist == | ||
# After Web Dev has approved the development of your project, immediately contact l10n-drivers to discuss your localization strategy. | |||
* Create a release schedule for your site so you can change content if needed | # Present a clear time-line so l10n-drivers can manage work flow to localizers | ||
: | # Prepare scope | ||
* Create templates that separate logic from localizable content | ** Length of content for the site | ||
** Functionality of site | |||
** Locales affected | |||
# Create a release schedule for your site so you can change content if needed | |||
# Make your project's file type decision. See [[L10n:Requirements/Web_l10n_filetypes]] | |||
** html | |||
** .lang | |||
** Gettext | |||
# Create templates that separate logic from localizable content | |||
# Set up a version control system (preferably SVN, since our localizers are familiar with it) | |||
# Set up a staging server | |||
# Notify QA lead that l10n is a requirement | |||
# 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 | *# Localizers will not start working until there is final sign off | ||