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

Hello HTML WG,

The Internationalization Core Working Group discussed I18N-ISSUE-17, related to making UTF-16 invalid as a character encoding for Polyglot documents. Our working group has tasked me with communicating our position on this, which is that we have no objection to forbidding this encoding.

I have also updated the bug with a pointer to this email.

Thanks (for I18N),

Addison

Addison Phillips
Globalization Architect (Lab126)
Chair (W3C I18N WG)

Internationalization is not a feature.
It is an architecture.

> -----Original Message-----
> From: Paul Cotton [mailto:Paul.Cotton@microsoft.com]
> Sent: Sunday, March 27, 2011 8:02 AM
> To: Phillips, Addison; 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]
> 
> >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.
> 
> Has this formal response been filed?  There does not seem to be an update to
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=12242

> 
> /paulc
> 
> Paul Cotton, Microsoft Canada
> 17 Eleanor Drive, Ottawa, Ontario K2E 6A3
> Tel: (425) 705-9596 Fax: (425) 936-7329
> 
> 
> -----Original Message-----
> From: Phillips, Addison [mailto:addison@lab126.com]
> Sent: Sunday, March 20, 2011 12:43 PM
> To: Paul Cotton; 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]
> 
> > 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 Monday, 28 March 2011 15:54:34 UTC