JosephMajaseSithole / datejs

Automatically exported from code.google.com/p/datejs
0 stars 0 forks source link

[INVALID] European date formats #13

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Type in 05/11/07 to the test textbox
2.
3.

What is the expected output? What do you see instead?
In the USA you would expect to see this resolved as 11th May (which is what
is displayed) but in Europe you would expect to see 5th November.

If you type in 23/11/07 this is correctly interpreted as 23rd November - so
where there is no ambiguity - there is no problem.

Would it be possible to use system information from the browser to correct
this?

What version of the product are you using? On what operating system?
Current test screen running in up to date FireFox

Please provide any additional information below.

Otherwise it all looks brilliant

Original issue reported on code.google.com by Chantalo...@gmail.com on 28 Nov 2007 at 4:21

GoogleCodeExporter commented 8 years ago
Please check out the Getting Started with Datejs tutorial. 
http://www.datejs.com/2007/11/27/getting-started-with-datejs/

Currently the library supports 150+ cultures and including the appropriate
culture-specific date.js file the Parser will automatically switch to the 
correct
parsing order for your country/culture/language.

The sample on the Datejs home page uses the "en-US" CultureInfo file which 
expects a
dateElementOrder of "mdy". We're in Canada and use the "date-en-CA.js" file in 
all
our internal apps. In Canada the expected dateElement order is "dmy".

The full download package includes all 150+ pre-compiled CultureInfo files. See
http://www.datejs.com/download/

Hope this helps.

Original comment by geoff%co...@gtempaccount.com on 28 Nov 2007 at 11:29

GoogleCodeExporter commented 8 years ago

Original comment by geoff%co...@gtempaccount.com on 27 Mar 2008 at 10:22