ecmascript at norbertlindenberg.com
Thu Jan 19 09:43:19 PST 2012
But time zones other than UTC and the "host environment's current time zone" are not supported. This limitation exists in version 1 of the API spec because one implementation currently doesn't support other time zones. We hope that in the next version this limitation can be removed and all IANA time zone names be supported.
The specification references Unicode Technical Standard 35 - that's not a version number, but the number of the document within the set of Unicode Technical Reports:
On Jan 19, 2012, at 9:06 , Nebojša Ćirić wrote:
> We do support UTC and local timezone (whatever it may be). The actual representation of the time zone will differ among platforms (GMT-7, Los Angeles/Pacific...).
> 18. јануар 2012. 22.16, Oliver Hunt <oliver at apple.com> је написао/ла:
> Unfortunately I'm not feeling well so I doubt I'll make tomorrows meeting.
> Here's some feedback on the globalisation API, from people who are more knowledgeable in these matters than I (although not JS experts :D ).
> * Near the bottom of page 31 [labeled page 25], there is a small typo: "[[ocaleData]]"
> * It seems to be bailing on requiring time zone support, other than for UTC. So, no formatting of dates into local times? (except a provided by implementation-specific extensions to this standard, perhaps)
> There was some other stuff but it may have been due to confusion over whether UTS v35 or v36 was intended (I assume this means more to others than to me). Once I've got it clarified I'll pass it on.
More information about the es-discuss