Status: New
Owner: ----
CC: kasperl%[email protected]
Labels: Type-Bug Priority-Medium
New issue 1290 by [email protected]: Date.toLocaleString() returns
invalid characters
http://code.google.com/p/v8/issues/detail?id=1290
The timezone portion of date strings is not showing up correctly on some
systems.
In the Chromium issue
(http://code.google.com/p/chromium/issues/detail?id=77610), a user is
getting a timezone of:
(Mitteleurop�ische Sommerzeit)
However their expectation is to have:
(Mitteleuropäische Sommerzeit)
The UTF16 codepoint of the funky character is 0xfffd.
I haven't reproduced this myself, however I suspect the problem is in:
http://code.google.com/p/v8/source/browse/trunk/src/platform-win32.cc
It retrieves a wide string from the OS, and then uses "%S" format specifier
to shove it into a char[] buffer. The caller in Date expects this string to
be UTF8. I don't actually understand what %S does, but it might be using
the system default codepage rather than resulting in UTF8, which means the
output is incorrect.
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
