On Aug 21, 2006, at 6:42 PM, Brian Kirsch wrote:
As it stands right now - correct. That's not to say at some later point I could get fancy and allow for a list of locales to be "active" - but that's definitely v2.0 stuff and parsedatetime hasn't hit 1.0 yet :)Yes it would be great to start thinking about this as your multi-lingual users will certainlyappreciate it.
Cool - I'll add it to the todo list.
How do the other natural language strings such as "dinner" get localized?Right now they are localized within parsedatetime itself. The current code has a number of python lists that contain special words and phrases that are used during different parts of the parsing.The new localizable code I'm working on moves those lists into a class that can be defined/overridden to define new locales. I was thinking of allowing for a "register a word lookup function" to allow the lists to be initialized by running them thru that function to create the localized versions.Might I offer a suggestion that you take a look at the gettext API.I think it will be much easier for you as the maintainer in the long runto have the parse tokens defined in a well defined standard such as the .po format. An open source on-line repository such as pootle can then be used for the creation and management of translations from the community via its web interface. Chandler of course also uses the .po format so it would be great for interoperability :)
A most excellent suggestion! I'll change the code to take advantage of gettext after I get it working with internal classes.
Thanks! --- Bear Build and Release Engineer Open Source Applications Foundation (OSAF) [EMAIL PROTECTED] http://www.osafoundation.org [EMAIL PROTECTED] http://code-bear.com PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29
PGP.sig
Description: This is a digitally signed message part
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
