- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 02 Apr 2009 16:26:44 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6742 --- Comment #9 from Nick Levinson <Nick_Levinson@yahoo.com> 2009-04-02 16:26:43 --- I think I like the preference for UTF-8. It's already preferred in HTML5. I recall a preference in general authoring practice for UTF-8 anyway (and I use it in websites). But, since that sounds like it would require and not just prefer UTF-8 in the HTML5 standard, maybe someone with a preference for another charset would like to weigh in on why not UTF-8, so concerns are recognized. If UTF-8 is to be required, I would suggest that UTF-8 apply to the page. I would not suggest sitewide applicability given the possibility of mixing markup languages within a site, e.g., the practice of making sitemaps in XML though other pages be, say, HTML. The issue isn't specific to percent-encoding vs. encoding into character references; any system of encoding would pass the same problem. The issue is what and when to encode, and so the solution has to be timed and must preserve pre-encoding. I invited Yahoo's response, but so far I haven't heard. Do we know what specific bug Yahoo has? I don't think that generically having dereferenced a numeric character reference is their bug, unless we're saying that that particular NCR should not have been dereferenced or that any NCR in that context should not have been dereferenced, if we define the context. -- Nick -- 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 Thursday, 2 April 2009 16:26:54 UTC