- From: <bugzilla@jessica.w3.org>
- Date: Wed, 10 Feb 2016 21:09:37 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29445 --- Comment #2 from Abel Braaksma <abel.braaksma@xs4all.nl> --- I was just about to sum up other occasions, glad I just saw your comment. An odd rule indeed, I know I have had my share of head-scratching every now and then when trying to find out why spaces were added in real-world scenarios. Guess my fix then was too overzealous and I didn't oversee the implications. Thanks for pointing that out. I do think that we have a (small) conflict in the spec. We point to 5.7.2 Creating Simple Content, but there we write a different story about xsl:value-of. I think we should change the part where we say "the default separator is the single space", as that is clearly not always true: <quote> The strings within the resulting sequence are concatenated, with a (possibly zero-length) separator inserted between successive strings. The default separator is a single space. In the case of xsl:attribute and xsl:value-of, a different separator can be specified using the separator attribute of the instruction; it is permissible for this to be a zero-length string, in which case the strings are concatenated with no separator. In the case of xsl:comment, xsl:processing-instruction, and xsl:namespace, and when expanding a value template, the default separator cannot be changed. </quote> -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 10 February 2016 21:09:43 UTC