Re: Issue 3607 in chromium: date.toLocaleString, toLocaleDateString and toLocaleTimeString are not locale-dependent

[chro...@googlecode.com]

Comment #14 on issue 3607 by theevancarroll: date.toLocaleString,
toLocaleDateString and toLocaleTimeString are not locale-dependent
http://code.google.com/p/chromium/issues/detail?id=3607

http://code.google.com/p/chromium/issues/detail?id=69884
potentially related.

[chro...@googlecode.com]

Comment #15 on issue 3607 by mieli...@gmail.com: date.toLocaleString,

toLocaleDateString and toLocaleTimeString are not locale-dependent
http://code.google.com/p/chromium/issues/detail?id=3607

Chrome 11.0.672.2 dev/Win7, the results for toLocaleString is inconsistent:

toLocaleDateString: "Saturday, February 26, 2011"
toLocaleTimeString: "22:26:19"
toLocaleString: "Sat Feb 26 2011 22:26:19 GMT+0100 (Central European
Standard Time)"
toString: "Sat Feb 26 2011 22:26:19 GMT+0100 (Central European
Standard Time)"

[chro...@googlecode.com]

Comment #18 on issue 3607 by sha...@irschad.de: date.toLocaleString,

toLocaleDateString and toLocaleTimeString are not locale-dependent
http://code.google.com/p/chromium/issues/detail?id=3607

Why WontFix all Browser can do it right, just Chrome not

[chro...@googlecode.com]

Updates:
Status: Assigned
Owner: c...@chromium.org
Labels: -Area-WebKit

Comment #19 on issue 3607 by js...@chromium.org: date.toLocaleString,

toLocaleDateString and toLocaleTimeString are not locale-dependent
http://code.google.com/p/chromium/issues/detail?id=3607

There's a now a proposal to implement toLocale* in terms of EcmaScript I18n
API.

See
http://norbertlindenberg.com/2012/06/ecmascript-internationalization-api/index.html
and
http://wiki.ecmascript.org/doku.php?id=globalization:specification_drafts

and http://code.google.com/p/v8-i18n

@cira, should we file this against v8-i18n or v8 ?

[chro...@googlecode.com]

Updates:
Blockedon: chromium:28604

Comment #20 on issue 3607 by js...@chromium.org: date.toLocaleString,

toLocaleDateString and toLocaleTimeString are not locale-dependent
http://code.google.com/p/chromium/issues/detail?id=3607

(No comment was entered for this change.)

[chro...@googlecode.com]

Comment #21 on issue 3607 by tk...@chromium.org: date.toLocaleString,

toLocaleDateString and toLocaleTimeString are not locale-dependent
http://code.google.com/p/chromium/issues/detail?id=3607

Issue 140675 has been merged into this issue.

[chro...@googlecode.com]

Updates:
Labels: WebKit-JavaScript

Comment #22 on issue 3607 by tk...@chromium.org: date.toLocaleString,

toLocaleDateString and toLocaleTimeString are not locale-dependent
http://code.google.com/p/chromium/issues/detail?id=3607

[chro...@googlecode.com]

Updates:
Status: Fixed

Comment #23 on issue 3607 by c...@chromium.org: date.toLocaleString,

toLocaleDateString and toLocaleTimeString are not locale-dependent
http://code.google.com/p/chromium/issues/detail?id=3607

v8-i18n library overrides v8 methods now and outputs locale appropriate
time/date/number. It doesn't check user settings on Windows, it uses
whatever CLDR data we have for the given default locale.

[chro...@googlecode.com]

Comment #28 on issue 3607 by xer...@gmail.com: date.toLocaleString,

toLocaleDateString and toLocaleTimeString are not locale-dependent
http://code.google.com/p/chromium/issues/detail?id=3607

Does not look fixed.
Just tested with v31 on Windows 8.1 Pro.

d = new Date(1292539800000);
document.write(d.toLocaleString());

prints: 12/16/2010 11:50:00 PM

My locale is Slovenian and the above appears to be American.

On the other hand
document.write(d.toString());

Prints: Thu Dec 16 2010 23:50:00 GMT+0100 (Central Europe Standard Time)
which is more correct. It show time in 24 hour format and the date part is
the same as with other browsers.

For comparison, IE11 prints:
- 16.12.2010 23:50:00
- Thu Dec 16 2010 23:50:00 GMT+0100 (Central Europe Standard Time)

Firefox 25:
- 16. december 2010 23:50:00
- Thu Dec 16 2010 23:50:00 GMT+0100 (Central Europe Standard Time)

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings