- From: Paul Cotton <Paul.Cotton@microsoft.com>
- Date: Sun, 20 Mar 2011 00:57:02 +0000
- To: Richard Ishida <ishida@w3.org>
- CC: "public-html@w3.org" <public-html@w3.org>, "Internationalization Core Working Group WG" <www-international@w3.org>
> 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 00:58:48 UTC