W3C home > Mailing lists > Public > public-webplatform@w3.org > November 2012

RE: Adding EcmaScript Internationalization API to webplatform.org

From: Eliot Graff <Eliot.Graff@microsoft.com>
Date: Tue, 6 Nov 2012 16:03:06 +0000
To: Nebojša Ćirić <cira@google.com>, "public-webplatform@w3.org" <public-webplatform@w3.org>
Message-ID: <CE3A5BFD1228D84A8D9C158EEC195FD53D9DC24E@TK5EX14MBXW602.wingroup.windeploy.ntdev.microsoft.com>
Hi Nebojša,

Thanks for the offer.

This is a wonderful opportunity for us to be crisp and clear about how we document emergent standards-based APIs that have yet to be implemented. Off the top of my head, I am not sure we have this part of the process documented anywhere, but if not, we should. And this API could be the poster child for the correct documentation process.

Eliot

From: Nebojša Ćirić [mailto:cira@google.com]
Sent: Monday, November 5, 2012 10:02 AM
To: public-webplatform@w3.org
Subject: Adding EcmaScript Internationalization API to webplatform.org

The v1.0 draft<http://wiki.ecmascript.org/doku.php?id=globalization:specification_drafts> was approved at the TC39 meeting in September, and browser vendors are working on implementations (Chrome v24 will provide full support, Chrome v22 has it but prefixed). Take a look at http://code.google.com/p/v8-i18n/w/list for a quick overview.

I would like to add documentation about the API and use cases to the webplatform.org<http://webplatform.org>. Where would be a good place to put it? Quick browse of the repository hints at:
1. http://docs.webplatform.org/wiki/javascript, new subtopic Internationalization
2. http://docs.webplatform.org/wiki/javascript, under subtopic of "Other concepts"

I prefer option 1, because it makes it look less optional for a developer.

Regards,
  Nebojša Ćirić
Received on Tuesday, 6 November 2012 16:04:13 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:57:35 UTC