* Localization (both product UI and documentation)
We are going to want to have detailed documentation by the end of .7 on how to
submit a localization of Chandler.
The .7 submission process may or may not be web UI based depending on
implementation time.
However, by .8 I envision:
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.
--Brian
Brian Kirsch - Cosmo Developer / Chandler Internationalization Engineer
Open Source Applications Foundation
543 Howard St. 5th Floor
San Francisco, CA 94105
http://www.osafoundation.org
Pieter Hartsook wrote:
On 4/10/06, Ted Leung <[EMAIL PROTECTED]> wrote:
I've put the notes of the more recent Portal Project meeting up on the wiki:
<http://wiki.osafoundation.org/bin/view/Journal/PortalProjectMtg20060407>
[snip]
We're going to move our discussions on the taxonomy onto this list, so you
can expect to see more traffic on this topic.
[snip]
Ted
A couple of additions to the "Becoming Part of the Community" section:
* End user documentation (user manuals, FAQs)
I don't think we need a "For Press" link in the sidebar on the wiki.
We'll have that link at the www.osafoundation.org site, and should
also have appropriate links on each of the product websites (formerly
knows as landing pages), location TBD, but possibly located on the
"Overview" pages AND from the FAQ pages.
Pieter
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general
