[Chandler-dev] .7 i18n Roadmap
bkirsch at osafoundation.org
Thu Apr 20 14:43:02 PDT 2006
Been busy off in Cosmo land but wanted to send a high level email
detailing the .7 plans related to internationalization.
The end goal for .7 is plausible localization in Western languages. One
should be able to, following simple steps translate Chandler
in to an alternate Western / romance language (French, Spanish, Italian,
To support this OSAF will take advantage of its in house translation
team (Andi and Philippe) and ship .7 with a French localization.
We will also accept localizations from the community. Although the
acceptance process in .7 is still to be determined.
By .8 a formalized means to edit, comment, and maintain localizations
will be provided via a web interface on top of a source control system.
The main new feature that will appear in .7 is Python eggs and egg
support for localized resources.
When a parcel or module is eggified, there will be a means to specify
the localized meta data that will ship with the egg.
This includes translation data files (.po) and resources such as images,
HTML help files, etc.
Although the specifics of how this will be accomplished still need to be
hammered out some general ideas have already been proposed
and hopefully during sprint week the remaining details can be solidified.
A reorganization of the current localization code in the i18n package
will also take place.
1. The i18n package will be moved under the osaf package.
2. The internal i18n code will be re-evaluated and augmented with the
intent of being a general Python i18n framework that developers can
leverage for non-Chandler projects.
At the schema level the Byte type will be deprecated as the Text type
now supports Unicode and ASCII.
Developers needing to store textual data in its original character set
should use a Repository Lob.
Speaking of Lob's, the body attribute on ContentItem is being changed
from a Lob to the Text type.
The displayName attribute will also be reworked to some extent. Most
likely an alternate attribute such as title will be introduced to
support localization. The specifics are still being decided.
I sent a email earlier today detailing my thoughts on the displayName
The dialog code needs to be CPIAfied and leveraging the Chandler
In addition, Chandler needs to leverage the .po translations that ship
So again the main end goal for .7 is a localized French version of
Chandler and the ability for the community to provide translations for
other Western languages.
Below are the open tasks which will need to be completed to reach this
3824 nor P3 All jed at osafoundation.org ASSI CPIA
needs to get font and color information from host OS
5618 nor P3 All pbossut at osafoundation.org ASSI The
Chandler splash screen needs to be localized.
4063 nor P4 All pje at telecommunity.com ASSI Move
the chandler.pack including displayName redirection ...
4067 nor P4 All pje at telecommunity.com ASSI
Localization of who, about, and date headers required
5658 nor P3 All bkirsch at osafoundation.org NEW
Localized UI meta data stored in the Repository needs to ...
2816 nor P3 All bkirsch at osafoundation.org ASSI
Translation of Chandler to French
4457 nor P3 All bkirsch at osafoundation.org ASSI
Revisit i18n file pathing
5457 nor P3 All bkirsch at osafoundation.org ASSI
Date and time format should follow OS - wanted to see Eur...
3576 nor P3 All davids at osafoundation.org ASSI
Dialog code reorganization for localization and PyICU sup...
Brian Kirsch - Cosmo Developer / Chandler Internationalization Engineer
Open Source Applications Foundation
543 Howard St. 5th Floor
San Francisco, CA 94105
More information about the chandler-dev