Re: Adding EcmaScript Internationalization API to webplatform.org

Fabulous - pass it on when you're ready!

Chris Mills
Open standards evangelist, Opera Software
W3C fellow
Co-chair, web education community group, W3C

* Author of "Practical CSS3: Develop and Design"
  (http://my.opera.com/chrismills/blog/2012/07/12/practical-css3-my-book-is-finally-published)
* The definitive guide to developing with the webplatform:
  http://www.webplatform.org

On 7 Nov 2012, at 11:52, Scott Rowe <scottrowe@google.com> wrote:

> Thanks Chris! I really appreciate your insights and help with this. I'll have something to show soon!
> +Scott
> 
> 
> 
> On Wed, Nov 7, 2012 at 8:19 AM, Chris Mills <cmills@opera.com> wrote:
> I'm happy to help draft a process about this. keep a record of what you did, then I can get it written up and tweaked, if you want some help of course ;-)
> 
> Chris Mills
> Open standards evangelist and dev.opera.com editor, Opera Software
> Co-chair, web education community group, W3C
> Author of "Practical CSS3: Develop and Design" (http://my.opera.com/chrismills/blog/2012/07/12/practical-css3-my-book-is-finally-published)
> 
> * Try Opera: http://www.opera.com
> * Learn about the latest open standards technologies and techniques: http://dev.opera.com
> * Contribute to web education: http://www.w3.org/community/webed/
> 
> On 6 Nov 2012, at 21:15, Scott Rowe <scottrowe@google.com> wrote:
> 
> > Hi all,
> >
> > I'm actually in the middle of developing a proposal for the apis documentation using WebRTC as the poster child. I've uncovered many problems, and I will propose solutions in the write-up. I hope to have it complete by the end of the week.
> >
> > +Scott
> >
> >
> >
> > On Tue, Nov 6, 2012 at 10:08 AM, Nebojša Ćirić <cira@google.com> wrote:
> > 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.
> >
> > The API is stable it's just not available in all browsers yet (Firefox is probably next to have support after Chrome, then IE).
> >
> > 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.
> >
> > How should we go about that? Should I just post the docs under JavaScript/Internationalization for now, then move them if new process emerges?
> >
> >
> >
> > 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 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. 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ć
> >
> >
> >
> >
> > --
> > Nebojša Ćirić
> >
> 
>

Received on Wednesday, 7 November 2012 16:54:40 UTC