1. A localizer registers or is granted an account.
2. The localizer logs in and can either create a new localization or review and comment on current localizations.
3. Creating a new localization takes the community member to an HTML form page where the English text entries are displayed next to localization form fields.
4. A new localization can either start fresh from the English strings or inherit from another localization parent. The latter would list both the English text and the parent localization text next to a form field.

If no text is entered in the form field the default parent value is used.

For example, a French Canadian (fr_CA) translation and a French (fr) translation would be very similar. The French Canadian localizer can inherit from an already completed French translation and only provide the text that differs between the two.

Once a translation is complete it is placed in a review queue where other community members who speak the language of the localization can confirm that the translation is accurate. How the confirmation takes place is still to be determined but a peer review system ala bugzilla would do the job nicely.

With each release translations will need to be maintained and augmented. The process is very similar. A diffing tool is used to determine additions, changes, and removal of English strings.

A translator will be asked to localize via the web UI only those fields that have changed or were added with the release.

-- MimiYin - 11 Apr 2006