W3C home > Mailing lists > Public > www-international@w3.org > January to March 2011

RE: I18N-ISSUE-17: UTF-16 an invalid encoding in Polyglot Markup [Polyglot]

From: Phillips, Addison <addison@lab126.com>
Date: Sun, 20 Mar 2011 09:42:52 -0700
To: Paul Cotton <Paul.Cotton@microsoft.com>, Richard Ishida <ishida@w3.org>
CC: "public-html@w3.org" <public-html@w3.org>, Internationalization Core Working Group WG <www-international@w3.org>
Message-ID: <131F80DEA635F044946897AFDA9AC3476A6662A325@EX-SEA31-D.ant.amazon.com>
> I am assuming that this email might be a notification that the I18N WG is going
> to take up this matter.  If so, when do you expect to complete any discussion?

The Internationalization Core Working Group has scheduled this item for discussion in our next teleconference, which will be Wednesday, 23 March, with a formal response to follow. This note is the result of Richard creating a tracker issue that we can use to track our WG response. It is not a request for the HTML WG to do anything. Sorry for any confusion. 

Addison

Addison Phillips
Globalization Architect (Lab126)
Chair (W3C I18N, IETF IRI WGs)

Internationalization is not a feature.
It is an architecture.

 

> -----Original Message-----
> From: www-international-request@w3.org [mailto:www-international-
> request@w3.org] On Behalf Of Paul Cotton
> Sent: Saturday, March 19, 2011 5:57 PM
> To: Richard Ishida
> Cc: public-html@w3.org; Internationalization Core Working Group WG
> Subject: RE: I18N-ISSUE-17: UTF-16 an invalid encoding in Polyglot Markup
> [Polyglot]
> 
> > Please add comments to bugzilla:
> > http://www.w3.org/Bugs/Public/show_bug.cgi?id=12242

> 
> I am trying to understand this text in this email.  Are you asking that these
> comments be added to bug 12242?  If so,  is there any reason why someone
> from the I18N WG cannot do that themselves?
> 
> > The i18n WG should see whether there is consensus on that approach.
> 
> I am assuming that this email might be a notification that the I18N WG is going
> to take up this matter.  If so, when do you expect to complete any discussion?
> 
> /paulc
> 
> Paul Cotton, Microsoft Canada
> 17 Eleanor Drive, Ottawa, Ontario K2E 6A3
> Tel: (425) 705-9596 Fax: (425) 936-7329
> 
> 
> -----Original Message-----
> From: public-html-request@w3.org [mailto:public-html-request@w3.org] On
> Behalf Of Internationalization Core Working Group Issue Tracker
> Sent: Friday, March 18, 2011 2:13 PM
> To: www-international@w3.org; public-html@w3.org
> Subject: I18N-ISSUE-17: UTF-16 an invalid encoding in Polyglot Markup
> [Polyglot]
> 
> 
> I18N-ISSUE-17: UTF-16 an invalid encoding in Polyglot Markup [Polyglot]
> 
> http://www.w3.org/International/track/issues/17

> 
> Raised by: Richard Ishida
> On product: Polyglot
> 
> 3. Specifying a Document's Character Encoding http://dev.w3.org/html5/html-

> xhtml-author-guide/html-xhtml-authoring-guide.html#character-encoding
> 
> WG Approved: No
> 
> Previously the polyglot document allowed only UTF-8 and UTF-16 encodings.
> Leif Silli has proposed that only UTF-8 be allowed, and the editor of the polyglot
> document has changed the specification to say that.
> 
> The i18n WG should see whether there is consensus on that approach.
> 
> Please add comments to bugzilla:
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=12242

> 
> 
> 

Received on Sunday, 20 March 2011 16:43:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 20 March 2011 16:43:39 GMT