User:IulianU/TransZilla

TransZilla is a tool for localisation of Mozilla-based apps. It is especially aimed at helping with Firefox/Thunderbird source-level localisation.

What you can do with it

• Read mozilla-style l10n trees (with dtd files and property files)
• Easily view added/changed/deleted strings in the original locale, and also changed strings in the destination locale (if you have more than one person in your translation team)
• Output l10n files maintaining the original structure of the file intact. That includes comments, annotations; spacing is preserved too. This makes TransZilla very CVS- and diff-friendly.

Getting started

1. Download the latest build of XULRunner 1.9a1 from http://ftp.mozilla.org/pub/mozilla.org/xulrunner/nightly/latest-trunk/
2. Get TransZilla from [here] and unpack it in a folder on your disk.
3. Unpack XULRunner in a subfolder named xulrunner of the TransZilla folder.
4. Create a l10n project file, based on the following example (using en-US and ro):

1. Start TransZilla using run.cmd (on Windows) or run.sh (on Linux)
2. It's important to start off with a consistent translation, i.e. your ab-CD tree should be a good consistent translation of the en-US tree that you have. You may want to use compare-locales.pl to make sure of this. We will arrive at updating the trees in a moment.
3. Choose Open, then open your l10n project.
4. Hit Refresh to populate the string database. This will take a long time - around 30 secs
5. Initially all strings will be marked fuzzy. To
6. Now that you've bootstrapped the string database, you can CVS update the source (en-US) and destination trees.
7. Hit Refresh again, to read the latest changes in the source and destination trees. It'll take a long time this time too.
8. Now you can start translating :-) New strings are red, changed (fuzzy) strings are on a yellowish background. Unchanged strings are in black. To hide those, uncheck the "translated" checkbox at the top of the list.
9. After you've done translating, hit "Merge back". This will incorporate your translation back into the destination tree. This will again take a long time.
10. Now you can CVS commit the changes in the destination tree, or maybe create a patch and send it to your locale owner.
11. At this point you can safely close TransZilla. Whenever you want to do another round of translation, just go back to step 6.

How you can help

• Report bugs
• Send in patches :-)
• Translate the app itself into your language

TODO list

• New project wizard
• Use progress bars to give feedback of long operations (refresh, mergeback, etc)