Please do not reply to this email- if you want to comment on the bug, go to the URL shown below and enter your comments there.
Changed by [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=78569 --- shadow/78569 2006-06-07 04:33:18.000000000 -0400 +++ shadow/78569.tmp.27043 2006-06-07 06:33:37.000000000 -0400 @@ -122,6 +122,18 @@ Other cultures might have got broken as well. For this particular case, there is another matching pattern M/d/yyyy h:mm:ss in en-GB DateTimeFormat (try new CultureInfo ("en-GB").DateTimeFormat.GetAllDateTimePatterns()). For such cultures that do not have conflicting date time patterns wouldn't have been affected. + +------- Additional Comments From [EMAIL PROTECTED] 2006-06-07 06:33 ------- +I really do think that the problem is in locale-builder. + +If you look at the output from [1], you'll see that the pattern +MM/dd/yyyy (from supp/en.xml) appears /before/ dd/MM/yyyy (from +locales/en_GB.xml). This is obviously incorrect as DateParse.Parse +will match the first pattern (from supp/en.xml) before the correct +pattern (from locales/en_GB.xml). + +[1]: +new CultureInfo("en-GB").DateTimeFormat.GetAllDateTimePatterns() _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
