L10n:Home Page | L10n:Localization Teams | L10n:Tutorial | L10n:Grackle_localization_tutorial
Contents |
In order to work on Flock Grackle localization, you don't need anything beside of one of the supported OS (Windows, Mac OS X, Linux) and a text editor.
First, check L10n:Localization_Teams and L10n:Teams_Currently_Forming in order to verify that there are no other people volunteered to work on your locale. If there are, contact them and cooperate, if there are none add your self. If you fail to get any response, mark their nicknames as "inactive" and step in. In case of any problem or lack of response from listed volunteers contact Israel Saeta.
Add yourself to Flock l10n maillist. All news about Localization will be posted there.
Second, check if there exists Localization Team for Firefox for your locale. It will be a lot easier if you'd decide to reuse Firefox localization. We also made it possible to reuse Firefox localization and overwrite files that you want translate on your own (for consistency or quality reasons), or you can localize everything from the scratch. Here you can view Fx l10n.
Currently, Flock provides two ways to localize it, first one, is to use a zip package delivered by Flock team, and send it back. It allows you to localize without any tool, but has a drawbacks like, it's harder to test your localization, or that if you'll find a bug, you need to send updated file to Flock team and wait for the update. Another method is to use SVN repository on your own. Since Flock stores all localizations in SVN (web view) you can simply get SVN account for yourself, and manage your localization on your own. Adventage of this method is that you don't have to wait for Flock team with any updates, and you can test your localization on your own.
If you will choose SVN method, you can pull SVN directory, and build Flock on your own with your localization in order to test its quality. Also, remember, that in order to test Flock, you need to build Flock. For instructions about how to build Flock - visit Fbuild.
Once you have your Flock build, just skip to the section about adding localization to already existing build.
Now you need to choose your method and skip to the section related to chosen one.
You need to have SVN client for your platform.
If you have perl on your machine, you also should download compare-locales.pl script. It will allow you to cross check your localization with english version for missing entities.
In order to be able to write into repository, you need to get SVN account. You can either file a bug in product Flock, component Internationalization with title in form "Localization account for ab-CD; email@domain.tld", indicating the nickname you'd want to use.
pull Flock l10n trunk:
svn co svn://svn.l10n.flock.com/l10n
pull en-US Flock from grackle branch which is 100% localization ready.
svn co svn://svn-mirror.flock.com/master/flock/branches/grouse/mozilla/flock/locales
Now you can start
First, build Flock using FBuild. Then get SVN access, and using locale_set script choose your locale (locale_set ab_CD - if there is no locale directory in trunk, you need to add it first). Then, erase $o/dist/bin directory and rebuild fbuild.sh. Once it's ready, you have flock in your lanuage. Now, you can edit $m/../l10n/ directory, write updates to svn, and rebuild Flock with updated locales by fbuild.sh.
locale_set not only pulled Flock localization but also Firefox localization for your locale. It means, that beside of $m/../l10n/ab-CD/flock directory which you need to localize, there's also a lot of Firefox directories pulled from CVS. You can overwrite any of those files and add them to SVN to make Flock use your version of those files instead of original ones.
More about practices at L10n:Tutorial.