Difference between revisions of "Release 0.2.3 Instructions"
m (Fixed bug link to newer bug) |
|||
| Line 2: | Line 2: | ||
== Release 0.2.3 for Mozilla Auto l10n (localization) tool == | == Release 0.2.3 for Mozilla Auto l10n (localization) tool == | ||
*Bug for this tool: | *Bug for this tool: | ||
| − | https://bugzilla.mozilla.org/show_bug.cgi?id= | + | [https://bugzilla.mozilla.org/show_bug.cgi?id=403215 Bug 403215 - Python script that will help create from a translated locale a regional build] |
*Webpage for this tool: | *Webpage for this tool: | ||
http://zenit.senecac.on.ca/wiki/index.php/Automated_localization_build_tool | http://zenit.senecac.on.ca/wiki/index.php/Automated_localization_build_tool | ||
Latest revision as of 14:50, 17 November 2007
Release 0.2.3 for Mozilla Auto l10n (localization) tool
- Bug for this tool:
Bug 403215 - Python script that will help create from a translated locale a regional build
- Webpage for this tool:
http://zenit.senecac.on.ca/wiki/index.php/Automated_localization_build_tool
- Download the 0.1 Zip file:
https://bugzilla.mozilla.org/attachment.cgi?id=284789
Instructions
- Make sure you have Python for your platform:
- We used Python 2.5.1 for Windows (http://www.python.org/ftp/python/2.5.1/python-2.5.1.msi) which comes with an IDE and a shell in which you can eveluate python statements, programs, etc
- Once you have it, double click on "l10nMerge.py". Type: "en-GB". Next, it will ask you to press "return"
- Now if you check the folder where you are you should see these files:
- "colors - Copy.dtd.bak", "colors.dtd.bak" and "preferences.properties" These files have the same contents as their original files (without the .bak suffix) but with the string "color" changed into "colour"
Description
The tools reads every DTD file and properties file on the current directory, parses it using the parser that comes on Parser.py and makes the changes. The only change right now is the word "color" to "colour", independantly if it is uppercase/lowercase, and singular/plural. The regular expresion handles the return of line and the only makes the changes to the strings associated to an entity, it doesn't modify an entity name
For release 0.2, we want to have: -many regular expressions changes happening at the same time -walk though subfolders and make these changes in every subfolder
FYI, you can get all the subfolders with all the files that have to modified (DTDs, properties and others) 1) Get the l10n tools and testing script and libraries by checking them out: $> cvs -z3 -d:pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot co mozilla/tools/l10n mozilla/testing/tests/l10n 2) This will create a folder below the Mozilla folder called "l10n/en-CA": $> python tools/l10n/l10n.py en-CA
Conclusion: this folder with all the files to be translated will be used to run the 0.2 and see how it works
