[FIXED] next wed at 4pm

[GoogleCodeExporter]

LOVE YOUR WORK.

Date.parse('next wed at 4PM') returns:
Wed Jan 23 2008 04:00:00 GMT+1100 (EST)

The work around is:
Date.parse('next wed at 16PM')

Incidently Date.parse('next wed at 16AM'): (NOTE AM) returns
Wed Jan 23 2008 16:00:00 GMT+1100 (EST)

All tests were run using [date-en-AU.js]

Original issue reported on code.google.com by m.bry...@gmail.com on 17 Jan 2008 at 9:13

[GoogleCodeExporter]

Thanks for the report. 

I ran your samples through the "Mad Skillz" widget on the datejs home page and 
they
all appear to parse correctly.

Are you running these tests with the latest build from SVN?
(http://www.datejs.com/svn/). If not, I would recommend grabbing the latest 
version.
There's been a boat load of revisions since the Alpha-1 release. 

If you are using the latest build, then maybe the problem has something to do 
with
the TimezoneOffset. Let me know if you're running the latest code (or not) and 
we'll
go from there. 

Try the Mad Skillz widget as well.

The Mad Skillz widget just passes the input value through Date.parse(), and it's
always up to date with the latest build. 

Hope this helps.

Original comment by geoff%co...@gtempaccount.com on 17 Jan 2008 at 9:21

• Changed state: Started

[GoogleCodeExporter]

Original comment by geoff%co...@gtempaccount.com on 28 Feb 2008 at 5:28

• Changed title: [FIXED] next wed at 4pm
• Changed state: Fixed