It seems like the majority of this belongs in EcmaScript directly rather than being restricted to web-oriented uses of ES. I'm also unsure of the relevance of CommonJS to either WebAPI or ES as CommonJS is not part of either standards body. For example the use of "require" implies making CommonJS modules part of WebAPI, rather than any of the current modules proposals working through TC39.
--Oliver On May 20, 2010, at 4:45 PM, Nebojša Ćirić wrote: > There are a number of areas where JavaScript i18n APIs are deficient. Our > goal is to develop better client-side i18n API for JavaScript, and eliminate > need for big JavaScript libraries or server side processing. Eventually, we > want to make them a part of WebAPI (worked on by WebApp WG). Our proposal to > API is up at http://docs.google.com/Doc?id=dhttrq5v_0c8k5vkdh > > In a Phase 1, we would start with limited WebKit implementation (locale > implementation and date formatting). A Phase 2 would extend it to cover > collation, number/currency formatting, calendars... > > See bug https://bugs.webkit.org/show_bug.cgi?id=39451 for details (proposed > API, motivation, related chromium bug and WebApps thread we started). > > We would like to start prototyping Locale part of the API in next couple > weeks, both for JSC and V8, and we would appreciate your input wrt. proposed > API. > > We'll continue working with WebApps group on standardizing the API but we > would like to keep moving forward with the implementation too, thus > cross-posting on webkit-dev. > -- > > Nebojša Ćirić > _______________________________________________ > webkit-dev mailing list > [email protected] > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
_______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
