== Want to help??? - Project Contributor(s)Name ==* <font color='red'><strong>I would like to apply to Automatic Localization Fork Tool'' - This script, given a string multiple regular expressions substitutions. I have seen something like re.compile(bla bla bla). Could I collect locale and a set of regular expressions in rules, will create an array an iterate through it applying l10n source tree of the substitutions to a stringsame language but different region (e.g. en-IN from en-GB)* '''THE BUG''' - [https://bugzilla.mozilla.org/show_bug.cgi?? or something like id=403215 Bug 403215 – Python script that?</strong></font>will help create from a translated locale a regional build]* <font color=strike>'''THE BUG''green'><strong>We want to find out where our - [https://bugzilla.mozilla.org/show_bug.cgi?id=399014 Bug 399014 – we need an l10n-merge tool should be located inside the source tree</strong>]</fontstrike>

*[[User:Rueen|Rueen Fiez]] (rueen) [http://rueenfiez.wordpress.com Rueen's blog]- (Point of Contact)

*[[User:Armenzg|Armen Zambrano]] (armenzg) [http://armenzg.blogspot.com /search/label/auto%20l10n Armen's blogabout the project] == Releases ===== Release notes ===* 1.0 Release'''(DONE)'''** <strike>Find way to potentially optomize localization process. Also, add functionality so localization file for search engines is auto generated</strike>*<strike> 0.9 Release** Seperate browser Strings & Labels localization template from browser Search Defaults localization template** Fixed a bug (if the first char in KEY was different from first char in VALUE, localization changes would not take place)** Improved code's readability</strike>*<strike> 0.8 Release** Add feature that allows to change default dictionary </strike>*<strike>0.7 Release** Add feature that will allow to modify default search engines to target locale.** Test on full source tree - worked, ScreenShots here. </strike>*<strike>0.6 Release** Complete localization template functionality. Will provide “localizers” with a hassle free way of altering strings/dates/currency/default search engines/default RSS, to target locale.</strike>*<strike>0.5 Release** Complete fixing outstanding bugs** Validation code** If time permits, get the template generator functional. ''(That way its one less thing todo for 0.7 release)'' </strike>*<strike>0.4 release** Remove regex code and supporting methods** Optimize existing methods such as the directory walk method. (Small thing but necessary nonetheless)** Add new command line options such as an option to generate localization template and an option to turn on tool's verbose mode</strike>*<strike>0.3 release</strike>** <strike>Use of command line arguments rather than receiving user's input</strike>** <strike>Fix the key changing problem</strike>** <strike>Add more words to change in an l10n tree. But they are hard-coded :(</strike> ** <strike>Stop using .bak file (and make the changes permanent)</strike>** <strike>Generate a second l10n tree out of original with the changes</strike>*<strike>0.2 release</strike>** <strike>Given any directory as a starting point, should walk through all sub-directories and files and make changes based on translation rules</strike>** <strike>Add ability to update Properties files</strike>** <strike>Fix key changing problem ('''In progress/May go to 0.3 release''')</strike>** <strike>Add more "rules", for now we are testing by changing ''color'' --> ''colour'' ('''May go to 0.3 release''')</strike>** <strike>Allow user to enter localization folder (eg; en-GB) as input</strike>

== Project Name news ==There are some common news from the collaborators that should be written here rather than splitting it between the collaborators:* Apr. 18, 2008 - Release 1.0 is now available, localizing process is now optomized to be completed faster. New functionality also added, ability to automatically generate a localization template for the default search engines with predefined keys* Apr. 6, 2008 - Release 0.9 - Big change to the way localizer enters their changes. They must now enter String/Label localization changes in the "locale_template.properties" file and enter Search Default changes in the "locale_template_searches.properties" file. This seperation increases readability and avoids confusion when entering many localization values. Also fixed a critical bug found related to the first char of KEY being different than the first char of VALUE in properties files. * Mar. 23, 2008 - Release 0.8 - tool will now alter values in Firefox's default dictionary (this means even the spellchecker in Firefox will localize accordingly) * Mar. 9, 2008 - Updated 0.7 to 0.7.2 after running tests on a full source tree. Screenshots available here.* Feb. 29, 2008 - Release 0.7 is done. I added the ability to change the locale of the default search engines - located in '''/browser/locales/en-US/searchplugins/'''.* Feb. 20, 2008 - Release 0.6 is completed. The tool is now able to make changes dynamically based on the Key/Value pairs located in the Localization Template .properties file. This file must be located in the same directory as the tool itself for the tool to be able to output a new localized source tree.* Jan. 29, 2008 - Updated [https://bugzilla.mozilla.org/show_bug.cgi?id=403215 Bug 403215] with information regarding latest release as well as plans for future releases. Updated release features for 0.5 and 0.7.* Jan. 20, 2008 - Release 0.4 is completed. Program has now been turned into a ''real'' command line tool. Added several command line options. Can view them all by running '''"l10nFork.py -help"'''. Fixed a MAJOR bug left over from 0.3.2, the localized changes were not taking place, bug was found in the callback() function. Removed/Commented-out all Regex, left one since need it for testing purposes right now. By 0.7 Release, 100% of regex in callback() function will be removed.* Jan. 10, 2008 - Project's roadmap from '''0.3''' release to a '''1.0''' release posted. New releases will be available on a bi-weekly basis. Outline of new features for each new release available in the [http://zenit.senecac.on.ca/wiki/index.php/Automated_localization_build_tool#Project_Plan_.26_Description Project Plan & Description section]. Many general Wiki page updates. The tool is now called the Automated Localization Fork tool, or l10n Auto Fork for short.* Nov. 11, 2007 - Updated the contributions page.* Nov. 10, 2007 - l10nMerge tool updated from ''automated '0.2.2''' to '''0.2.3''' and available for download under the 0.2 Release Functionality & Features section. Added new feature (allow user to directly input localization [eg; en-GB] ), added lots of code documentation and debug sections.* Nov. 9, 2007 - Created new bug (403215) that will guide the discussion about our tool* Oct. 31, 2007 - It seems that a lot of things are going to be talked around l10n tools in general ([http://groups.google.com/group/mozilla.dev.l10n/browse_thread/thread/61f5742491a4d3fc " L10n tools talking" in Google Groups]) and specifically in the bug ([https://bugzilla.mozilla.org/show_bug.cgi?id=399014 Bug 399014]) ''"related"'' (between brackets) to our project. We will have to read dynamis' (he has finally appeared, he is called Asai Tomoya) code and see what the new direction of our script should take. <strike>'''WE ARE A LITTLE CONFUSED BUT AFTER THE WEEKEND SOME LIGHT MIGHT DROP INTO THE PROJECT'''</strike> ('''Done''')* Oct. 30, 2007 - Axel has replied on the bug and it seems that '''our project shouldn't be called l10n merge''', the bug seems to be for another reason. ''Some doubts arise concerning what our toolshould really be doing'' .* Oct. 25, 2007 - This Meeting with Michal; She explained us the different tools that out there created by the community and by next week will gives us more information on which direction to follow* Oct. 23, 2007 - Added 0.2 Release Functionality & Features section. Team meeting held (6 hours) - our toolis now able to, given a locale localization directory (or any directory for that matter), walk through all sub-directories and files and make changes based on our translation rules. We've also determined a set few other things to do before our 0.2 release and even brainstormed 0.3 ideas (incorporating l10n's setup.py script into our tool like Axel suggested).* Oct. 12, 2007 - Updated 0.1 Release Functionality & Features section. A lot of rulesthe 0.1 code has been done.* Oct. 07, create 2007 - Added an 0.1 Release Functionality & Features section to the wiki so we have a build clear description of the same what our project's 0.1 release should be able to do.* Oct. 05, 2007 - Python will be our language but different region of choice for this project which is a great opportunity to thoroughly learn it since it will be our first time using it. Determined some main tasks ahead of us before 0.1 release (etasks mentioned in [http://zenit.senecac.on.ca/wiki/index.php/Automated_localization_build_tool#Project_Description Product Description]).g* Sep. en24, 2007 -IN We are going to have a call conference with Michal from en-GB)Toronto office

== Project Description =Potential Ways of Contributing ===<strike>Python regular expressions help</strike>* <strike><u>Bug:</u> When parsing files that use key/value pairs - '''THE BUGDTD or Properties''' - [https://bugzilla.mozilla.org/show_bug.cgi?id=399014 Bug 399014 – we need an l10n-merge our tool]* Learn python* Understand not only changes the scripts from value but the test l10n tools* Understand key as well. We don't want the l10n build system* Reproduce en-IN from en-GBkey to be changed.</strike>* Determine what #Testing our Python based system will "do" in 0script when needed.1 (Usually right after a release)

== Releases ==<font color='red'>'''Our python script(I think shouldn't be called tool) since on the bug we can see that Axel was referring to something else, BUT we will keep it until a better name comes'''</font>=== Tool's 0.2 Release Functionality & Features ===* '''INSTRUCTIONS''': ''TBD''Vijey Balasundaram * '''Tool - 0.2 release ZIP file''': (''***Tentative release***'') [http://matrixTested our tool and looked for bugs or any potential future pitfalls we might run into.senecac.on.ca/~azambran/mozilla/l10nmerge0.2.2.zip l10nMerge2.0.2.zip Tool (0.2Helped with some documentation for first time tool users.2)]

#Given any directory as a starting point, should walk through all sub-directories * Mozilla l10n Community **Provided strong leadership and files and make changes based on translation rules ('''Done''')#Add ability to update Properties files ('''Done''')#Fix key changing problem ('''may go to 0support.3''')#Add more "rules", for now we are testing by changing We wouldn''color'' --> ''colour'' ('''may go t be able to 0get this project off the ground without them.3''')

=== Tool's 0.1 Release Functionality & Features ===* Seneca Professors * '''INSTRUCTIONS''': [http://matrix.senecac.on.ca/~azambran/mozilla/instructions0.1.txt TXT file]* '''Tool - 0.1 release ZIP file''': [https://bugzilla.mozilla.org/attachment.cgi?id=284789 Automated Localization Build Tool (0Put us in contact with the Mozilla l10n community and helped us get this project off the ground through structure and guidance.1)]

#Should be able ==== Contribution Info ====*<strike>I would like to apply to accept a localization string multiple regular expressions substitutions. I have seen something like re.compile('''Done'''bla bla bla)#Should be able . Could I collect a set of regular expressions in an array an iterate through it applying the substitutions to accept a Firefox build (eg; en-GB string?? or en-US) ('''Done''')something like that?</strike>#Read through every DTD and Properties file in the current directory with the "Parser*<strike>[http://zenit.senecac.on.ca/wiki/index.py" file php/User:Tjduavis Timothy Joseph Duavis] ('''Done'''here to be of service!)#Changes the word "color" to "colour" in every DTD file and have it saved </strike> ('''Done''')

== Other Project Details ==

* (...) what is inside the parentheses are a group - the contents of a group can be retrieved after a match has been performed, and can be matched later in the string with the ''\number'' special sequence * (?...) - This is an '''extension notation''' - Extensions usually do not create a new group; (?P<name>...) is the only exception to this rule. Following are the currently supported extensions. * List of supported extensions: (?iLmsux), (?:...), (?P<name>...), (?P=name), (?#...), (?=...), (?!...), (?<=...), (?<!...), (?(id/name)yes-pattern|no-pattern)

* '''THE BUG''' - There are no bugs related specifically to the project, but the following were mentioned in our conversations[https://bugzilla.mozilla.org/show_bug.cgi?id=403215 Bug 403215 – Python script that will help create from a translated locale a regional build]* * <strike>'''THE BUG''' </strike> - [https://bugzilla.mozilla.org/show_bug.cgi?id=399014 Bug 399014 – we need an l10n-merge tool]* [https://bugzilla.mozilla.org/show_bug.cgi?id=398954 Bug 398954 – l10n build automation doesn't pick the right en-US source for the build]* [https://bugzilla.mozilla.org/show_bug.cgi?id=391680 Bug 391680 – Make the python compare-locales work with suite and calendar]