- From: <bugzilla@jessica.w3.org>
- Date: Sun, 14 Aug 2011 18:02:32 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13771 --- Comment #11 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> 2011-08-14 18:02:31 UTC --- (In reply to comment #10) > Feel free to fix the page if you think it is not clear. And it is useful that > all technologies behave the same when it comes to encoding labels. Having > differences for legacy cruft is not needed. Better to be consistent. I think it can work OK w.r.t. such a longtime goal to implement this bug. XML parsers are not required to support more than UTF-8 and UTF-16. If removing support for the "US-ASCII" label means removing support for Windows-1252 (and its misinterpreted aliases) then this would mean that the XML parsers of the Web browses would not need fall for the temptation to interpret UTF-8 as WIN-1252 (like e.g. Opera and Webkit under some conditions currently do). It is not like the future of the Web is Windows-1252 - the future is UTF-8. And XML on the web is rather rare - and non-UTF-8 XML is probably even much rarer. Whenever the longterm goal you describe is reached, the Web browser's XML parsers, can consider enabling support for Win-1252 again, should they want to do that. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Sunday, 14 August 2011 18:02:33 UTC