User:IulianU/TransZilla: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 6: | Line 6: | ||
==Getting started== | ==Getting started== | ||
# Download the latest build of XULRunner 1.9a1 from http://ftp.mozilla.org/pub/mozilla.org/xulrunner/nightly/ | # Download the latest build of XULRunner 1.9a1 from http://ftp.mozilla.org/pub/mozilla.org/xulrunner/nightly/latest-trunk/ | ||
# Get TransZilla from [here] and unpack it in a folder on your disk. | # Get TransZilla from [here] and unpack it in a folder on your disk. | ||
# Unpack XULRunner in a subfolder named <tt>xulrunner</tt> of the TransZilla folder. | # Unpack XULRunner in a subfolder named <tt>xulrunner</tt> of the TransZilla folder. | ||
| Line 18: | Line 18: | ||
# Initially all strings will be marked ''fuzzy''. To | # Initially all strings will be marked ''fuzzy''. To | ||
# Now that you've bootstrapped the string database, you can <tt>CVS update</tt> the source (en-US) and destination trees. | # Now that you've bootstrapped the string database, you can <tt>CVS update</tt> the source (en-US) and destination trees. | ||
# Hit Refresh again, to | # Hit Refresh again, to read the latest changes in the source and destination trees. It'll take a long time this time too. | ||
# 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. | # 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. | ||
# After you've done translating, hit "Merge back". This will incorporate your translation back into the destination tree. | # 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. | ||
# Now you can <tt>CVS commit</tt> the changes in the destination tree, or maybe create a patch and send it to your locale owner. | # Now you can <tt>CVS commit</tt> the changes in the destination tree, or maybe create a patch and send it to your locale owner. | ||
# 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== | ==How you can help== | ||
Revision as of 16:10, 11 May 2006
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 l10n trees
- 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
- Download the latest build of XULRunner 1.9a1 from http://ftp.mozilla.org/pub/mozilla.org/xulrunner/nightly/latest-trunk/
- Get TransZilla from [here] and unpack it in a folder on your disk.
- Unpack XULRunner in a subfolder named xulrunner of the TransZilla folder.
- Create a l10n project file, based on the following example (using en-US and ro):
- Start TransZilla using run.cmd (on Windows) or run.sh (on Linux)
- 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. We will arrive at updating the trees in a moment.
- Choose Open, then open your l10n project.
- Hit Refresh to populate the string database. This will take a long time - around 30 secs
- Initially all strings will be marked fuzzy. To
- Now that you've bootstrapped the string database, you can CVS update the source (en-US) and destination trees.
- Hit Refresh again, to read the latest changes in the source and destination trees. It'll take a long time this time too.
- 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.
- 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.
- Now you can CVS commit the changes in the destination tree, or maybe create a patch and send it to your locale owner.
- 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)