- From: <bugzilla@jessica.w3.org>
- Date: Tue, 12 Oct 2010 09:52:46 +0000
- To: public-i18n-core@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10890 --- Comment #7 from Julian Reschke <julian.reschke@gmx.de> 2010-10-12 09:52:46 UTC --- For the record: I disagree with the "decision"; we already have special cases around here, and either way a special case is needed here. From my point of view, leaving it conformant when the document indeed is encoded in UTF-16 is more helpful than forbidding it. I'd recommend that the I18N WG to re-opens the issue. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You reported the bug.
Received on Tuesday, 12 October 2010 09:52:48 UTC