+1

Comments in line

Brian Kirsch - Email Framework Engineer
Open Source Applications Foundation
543 Howard St. 5th Floor
San Francisco, CA 94105
(415) 946-3056
http://www.osafoundation.org



Ted Leung wrote:


On Jan 5, 2006, at 1:00 PM, Brian Kirsch wrote:

That would be great.

The missing piece right now is linking translation file registration with pje's Python egg implementation. In .7 a set of localization files will be able to be distributed with an egg and additional translations will be able to be supplied out of band. For example, one could provide a French translation for all of Chandler or for a specific 3rd party parcel or for a set of parcels without having to place localization files in a specific directory under a specific folder root. That limitation is a part of the traditional gettext approach.
we want to take a more dynamic developer driven approach.

The specific details of how this is going to be done still need to be worked out for .7.

I'd like to figure out the timeline for this sooner rather than later.


Yes, this needs to be addressed in the next few weeks. In fact, it would be an excellent topic for the OSAF in house January sprints.



Once this feature is in the architecture then the localization process can take place.

By the end of .7, I would like to see at the very least a French and a Spanish translation shipping with the release.


I'd hope that once we can get the architecture stuff fixed, we could start enlisting people to provide translations. Long term, I think it would be great of most of these translations were done by people outside the OSAF staff.

By the end of .7 we will be ready to start accepting community translations although a more formal acceptance process for example submission and verification of translations through a web interface might have to wait till .8.

It has always been the goal that localization would be primarily a community operation.

taken from the Internationalization Wiki Project page (http://wiki.osafoundation.org/bin/view/Projects/InternationalizationProject):

"Community participation will play an import role in our I18N strategy. The OSAF team has neither the developer resources nor the linguistic expertise required to produce translations for the multitude of languages spoken across the globe. This is where we turn to our supporters to help provide translations. The team will be very responsive to the community and will work closely with localization developers. This includes making adjustments to the i18n road map based on the participation of the community. "





-Brian


Brian Kirsch - Email Framework Engineer
Open Source Applications Foundation
543 Howard St. 5th Floor
San Francisco, CA 94105
(415) 946-3056
http://www.osafoundation.org



Philippe Bossut wrote:

Brian Kirsch wrote:

Localization is probably not a good candidate for a Sprint at this time. The architecture is mostly in place but the missing pieces are too large to tackle in a one to two day session.

The only item I can think of that might work would be OS Locale lookup.

Query the native Operating System (Linux, OS X, Windows) for its Locale set and for any custom Date Time, Numeric, and Currency settings. This will require Swig wrapped C / C++ API code for each of the target platforms.



Fair enough and thanks for the info Brian. I was planning to start a French localization project myself in the coming months and Arnaud Estienne, a French volunteer, proposed to work on this as well. May be we should think about hosting such a sprint at EuroPython since it's in July, we'll have more experience with it and I and Arnaud could meet in person, may be with others interested in localization (better chance to meet them there...). What do you guys think? (Brian and Ted specifically).

BTW, Arnaud, are you here?... :) You told me you subscribed to the list but I haven't seen any intro email from you yet. May be it's a good time to pitch in and say 'hi'... :)


----
Ted Leung                 Open Source Applications Foundation (OSAF)
PGP Fingerprint: 1003 7870 251F FA71 A59A  CEE3 BEBA 2B87 F5FC 4B42


_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev

Reply via email to