1,035
edits
L10n:Starting a localization: Difference between revisions
Jump to navigation
Jump to search
→Going beyond language packs
(overhaul, restructure the page, add a dash of UX, too.) |
|||
| Line 28: | Line 28: | ||
= Going beyond language packs = | = Going beyond language packs = | ||
Working on a language | Working on a language packs has the advantage that your testers can get updates on your work much more easily, and it requires a lot less toolchain compared to doing fully localized builds. | ||
As mentioned in the [[L10n:Localization Process]], having language packs only comes with a few downsides for your users, in particular, the in-product web pages are not in your language, and the install and migration experience occurs in the language that your users installed first. Depending on your language, this may be more or less severe. Our common objective is to create fully localized official builds together, once you and your testers are comfortable with the localization work thus far. | |||
<div class="note">There are known issues with language packs between releases we are working to fix [[https://bugzilla.mozilla.org/show_bug.cgi?id=334136|bug 334136]].</div> | <div class="note">There are known issues with language packs between releases we are working to fix [[https://bugzilla.mozilla.org/show_bug.cgi?id=334136|bug 334136]].</div> | ||
| Line 34: | Line 36: | ||
To move forward from the stage of language packs, you would request to make your build official, which is described in the [[L10n:Localization Process Middle]]. | To move forward from the stage of language packs, you would request to make your build official, which is described in the [[L10n:Localization Process Middle]]. | ||
'''Useful tips.''' | '''Useful tips.''' We like to improve on this section, so if you feel you have some useful tips please feel free to edit this section with additional helpful sources of information. | ||