- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 20 Aug 2009 16:07:56 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6808 Henry Zongaro <zongaro@ca.ibm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Whitespacing rules are too |[Ser] Whitespacing rules are |restrictive for the indent |too restrictive for the |parameter |indent parameter --- Comment #1 from Henry Zongaro <zongaro@ca.ibm.com> 2009-08-20 16:07:55 --- Andy, thank you for your comment. I can think of a slightly thorny case that would make it somewhat difficult to word the extension to this feature in the way you've suggested. Consider the following example: <elem>some text<!-- a comment --><!-- a pithy remark --></elem> The first note in section 5.1.3[1] states, in part, "The effect of these rules is to ensure that whitespace is only added in places where... it does not affect the string value of any element node with simple content." So it wouldn't be sufficient to state that whitespace characters could be added before or after comments and processing instructions, as inserting some between the comments in the example above above would change the string value of elem, which might have simple content. Though it would be nice to permit a serializer some additional latitude, my recommendation would be not to fix this in an erratum, and defer consideration of any change until Serialization 1.1. This isn't a serious limitation as it stands. [1] http://www.w3.org/TR/2007/REC-xslt-xquery-serialization-20070123/#xml-indent -- 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, 20 August 2009 16:08:06 UTC