- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 12 Nov 2009 16:35:10 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8245 Henry Zongaro <zongaro@ca.ibm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #2 from Henry Zongaro <zongaro@ca.ibm.com> 2009-11-12 16:35:09 --- Yes, it's quite possible that an explicit enumeration of characters will become out of date. I had worried about that, but I was also concerned that the list of proscribed characters in HTML is so obscure that simply saying "such as" wouldn't be of much help to either implementers or users. (After seven years of experience with implementing XSLT, it took me about an hour to discover where the list appears. I'd like to save others that pain.) How would you feel about the following proposed edits, which list all the control characters, while still hedging by using "such as"? . In the third paragraph of section 7.3, change "specifically the control characters #x7F-#x9F, are legal in XML" to "such as the control characters #x1-#x8, #xB, #xC, #xE-#x1F and #x7F-#x9F, are legal in one or both versions of XML, but not in HTML" . In appendix B, in the definition of err:SER0014, delete ", specifically the control characters #x7F-#x9F," -- 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, 12 November 2009 16:35:12 UTC