Difference between revisions of "Automated localization build tool"
m (→Project Name) |
(→Project Description) |
||
| Line 9: | Line 9: | ||
* Reproduce en-IN from en-GB | * Reproduce en-IN from en-GB | ||
* Determine what our Python based system will "do" in 0.1 release | * Determine what our Python based system will "do" in 0.1 release | ||
| + | |||
| + | '''Tool's 0.1 Release Functionality & Features''' | ||
| + | * Should be able to accept a localization file | ||
| + | * Should be able to accept a Firefox build (eg; en-GB or en-US) | ||
| + | * Store's file's data locally (need to use IO if .txt file (or) XML Parser if it's an .xml file). So this would taking the key/value pairs and storing them in a Dictionary (Dictionary is the equivalent of a Map in Java) | ||
== Project Leader(s) == | == Project Leader(s) == | ||
Revision as of 15:53, 7 October 2007
Contents
Project Name
automated localization tool - This tool should allow that given a locale and a set of changes (unknown how) gives a build of the same language but different region (e.g. en-IN from en-GB)
Project Description
- Learn python
- Understand the scripts from the test l10n tools
- Understand the l10n build system
- Reproduce en-IN from en-GB
- Determine what our Python based system will "do" in 0.1 release
Tool's 0.1 Release Functionality & Features
- Should be able to accept a localization file
- Should be able to accept a Firefox build (eg; en-GB or en-US)
- Store's file's data locally (need to use IO if .txt file (or) XML Parser if it's an .xml file). So this would taking the key/value pairs and storing them in a Dictionary (Dictionary is the equivalent of a Map in Java)
Project Leader(s)
- Rueen Fiez (rueen) Rueen's blog
- Vincent Lam (vlam6) Vince's blog
- Armen Zambrano (armenzg) Armen's blog
Project Details
- Team notes - we collect notes related to the project
- Localization process - diary - You can read notes of what I've been trying
Project news
There are some common news from the collaborators that should be written here rather than splitting it between the collaborators:
- Sep. 24, 2007 - We are going to have a call conference with Michal from Toronto office
- Oct. 05, 2007 - Python will be our language 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 (tasks mentioned in Product Description).
