I 100% agree but, without a tool allowing us to help the program, I don't know how the code may guess that
1/2/2003 is a dd/mm/yyyy date or a mm/dd/yyyy one.
This why I wrote.
(3) is it foolish to ask for this kind of tool:
localizeDate("12/31/1943","US")
or
localizeDate("1943/12/31","IEEE")
or
localizeDate("11 september 2001","English")
localizeDate("12/31/1943","English")
localizeDate("14 juillet 1789","French")
localizeDate("14/07/1789","French")
localizeDate("1943/12/31","IEEE")
or the alternate Ed's proposal:
date someStringwithAdate using {region: "United States", calendar: "Gregorian")
The revised tool is described as giving a better support of internationalization.
At this time, I see a tool which works correctly only for English users receiving only mm/dd/yyyy dates.
This is why I used the word which hurted Mark J. Reed.
I will not repeat the word but my judjment is unchanged :
there are users of 1st class and users of 2nd class !
Yvan KOENIG (VALLAURIS, France) mardi 8 septembre 2009 09:38:05