Confirmed users, Bureaucrats and Sysops emeriti
2,976
edits
(minor updates are fixed, link to Cedric's tool) |
|||
| Line 30: | Line 30: | ||
Something to think about all throughout your work is [[L10n:Building_Blocks| expanding the community around you]] who can help you with the language you're working on. This is a good thing and will be useful for you for testing, celebratory events (i.e, launch parties), and possibly web pages or other areas you might need or want help with. We want to help you with this and are working on programs that we believe will do so. To read more about this, check out Seth's blog on our [http://blog.mozilla.com/seth/2007/06/04/support-update-3/ global program]. | Something to think about all throughout your work is [[L10n:Building_Blocks| expanding the community around you]] who can help you with the language you're working on. This is a good thing and will be useful for you for testing, celebratory events (i.e, launch parties), and possibly web pages or other areas you might need or want help with. We want to help you with this and are working on programs that we believe will do so. To read more about this, check out Seth's blog on our [http://blog.mozilla.com/seth/2007/06/04/support-update-3/ global program]. | ||
<div class="note"> | |||
'''You only have a language pack?''' | |||
There seem to be a bunch of language packs floating around still, that don't exist in an up-to-date form to be used for the build. If you have one, and would like to convert it to a source, [http://perso.orange.fr/cedric.corazza.net/html/langpack2cvstree.html there's a tool] by [http://perso.orange.fr/cedric.corazza.net/html/mozilla.html Cedric] that can help you with the file shuffling. The build process from sources to language packs is lossy, so there will be work left to do, but the tool will do the tedious part for you. | |||
</div> | |||
= Going beyond language packs = | = Going beyond language packs = | ||
| Line 36: | Line 41: | ||
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. | 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. | ||
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]]. | ||