dd-mm-yyyy format date enhancment

[GoogleCodeExporter]

I recently looked at parsedatetime. It looks great, but I can't use it
because I can't configure it to accept dates in the local (Australian)
format of dd-mm-yyyy. Any chance of supporting Aussie dates?

Original issue reported on code.google.com by alan.gr...@gmail.com on 4 Sep 2006 at 10:53

[GoogleCodeExporter]

It should be rather easy to do this and would be a great test of my initial
localization attempts.

What I would need is information on any other differences - or does it boil 
down to
dd-mm vs mm/dd ?

Is the time seperator ':', is 24hr time preferred, things like that.

Sorry for the delayed response - for some reason I figured I would get an email 
if
someone posted an issue.

Original comment by bear42 on 7 Sep 2006 at 5:49

[GoogleCodeExporter]

Original comment by bear42 on 7 Sep 2006 at 5:50

• Changed state: Started

[GoogleCodeExporter]

I did a quick check with ICU and it has locale en_AU listed as using / as the 
date
seperator.

What I'll do for now is create an internal pdtLocale_au that is set to all of 
the
info I get from ICU and then it can be adjusted based on the info you give me.

Original comment by bear42 on 7 Sep 2006 at 6:03

[GoogleCodeExporter]

Original comment by bear42 on 7 Sep 2006 at 6:03

[GoogleCodeExporter]

I checked into the trunk (revision 18) a first pass at making this work.

I created a pdtLocale_au to handle the en_AU locale if PyICU is not present.

Let me know if you need me to create a new tarball for you to test with.

Original comment by bear42 on 7 Sep 2006 at 8:53

[GoogleCodeExporter]

released 0.7.3 which contains the new code to alter how m/d/y dates are parsed 
to
honor locale specific information as to the order of 'm', 'd' and/or 'y'

Original comment by bear42 on 26 Sep 2006 at 3:30

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by bear42 on 14 Feb 2007 at 7:13

• Changed state: Verified