L10n:Pontoon/0.1alpha: Difference between revisions
Jump to navigation
Jump to search
(Add two ideas.) |
|||
| Line 27: | Line 27: | ||
#* Existing work flow will cause problems for localizers from different localization teams. The tool probably needs a clear list of locales where a user starts with a selection to begin work. | #* Existing work flow will cause problems for localizers from different localization teams. The tool probably needs a clear list of locales where a user starts with a selection to begin work. | ||
#* '''Measure of success:''' Testable tool with a clear work flow | #* '''Measure of success:''' Testable tool with a clear work flow | ||
# Silme support by allowing export to any format and not just Gettext | |||
# Auto-detection so we don't have to have a header | |||
== Other features, ideas, requests == | == Other features, ideas, requests == | ||
* Split list of strings which are available for translation to two list (what was translated, what is needed to translate) | * Split list of strings which are available for translation to two list (what was translated, what is needed to translate) | ||
* Locale autodetect. I should see my locale by default. | * Locale autodetect. I should see my locale by default. | ||
Revision as of 20:17, 9 February 2010
General Plan
- Individual leads needed for 0.1 release
- Dev lead (Gandalf)
- Dev backup (Fred?)
- Code review (Fred?)
Goal of this release
To release an experimental, but stable version of Pontoon for localizers to test on Mozilla websites.
Initial time-line
- Free hacking
- March 1, 2010 - API freeze
- March 15, 2010 - Code freeze
- March 30, 2010 - 0.1 Alpha Release
- Any external dependencies
Bugzilla
Feature Summary
- Back-end set up to handle html translations
- Team will need to work on stabilizing the client to server communication when a user has installed the tool
- Will need to make sure there are no conflicts if many users are using the tool on the same localization
- Measure for success: Tool is supported on a Mozilla server without major conflics
- Clean UI focusing on clear work flow
- Existing work flow will cause problems for localizers from different localization teams. The tool probably needs a clear list of locales where a user starts with a selection to begin work.
- Measure of success: Testable tool with a clear work flow
- Silme support by allowing export to any format and not just Gettext
- Auto-detection so we don't have to have a header
Other features, ideas, requests
- Split list of strings which are available for translation to two list (what was translated, what is needed to translate)
- Locale autodetect. I should see my locale by default.