1,035
edits
L10n:Starting a localization: Difference between revisions
→Going beyond language packs
| Line 34: | Line 34: | ||
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 [http://en.wikipedia.org/wiki/Toolchain toolchain] compared to doing fully localized builds. | 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 [http://en.wikipedia.org/wiki/Toolchain 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 | 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 thus far. | ||
<div class="note">There are known issues for language packs between minor releases of Firefox we are working to fix [[https://bugzilla.mozilla.org/show_bug.cgi?id=334136|bug 334136]].</div> | <div class="note">There are known issues for language packs between minor releases of Firefox we are working to fix [[https://bugzilla.mozilla.org/show_bug.cgi?id=334136|bug 334136]].</div> | ||
To move forward from the stage of language packs, you would request to make your build official, which is described in the [[L10n:Becoming_an_Official_Localization]]. | To move forward from the stage of language packs, you would request to make your build official, which is described in the [[L10n:Becoming_an_Official_Localization]]. | ||