- From: <bugzilla@jessica.w3.org>
- Date: Mon, 14 Jan 2013 10:50:28 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16311 Henry Zongaro <zongaro@ca.ibm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #11 from Henry Zongaro <zongaro@ca.ibm.com> --- Jidanni, sorry for the late update on this issue. At the joint teleconference of the XSLT and XQuery working groups of 25 September 2012,[1] the working groups decided to resolve your request through the addition of a new "item-separator" serialization parameter. The item-separator is a string, and if present, each item in the serialized result is separated by its value. The serialization parameter affects all output methods, not just the text output method. So, if the sequence to be serialized was <X>1</X>,<Y>2</Y>, and the value of the item-separator was the LINE FEED character, the serialized result for the XML output method would be <X>1</X> <Y>2</Y> and for the TEXT output method would be 1 2 Note that the value of the parameter is only inserted between items in the original sequence that is to be serialized. So if the value of the item-separator was LINE FEED, and the sequence to be serialized under the TEXT output method was <p>My <em>first</em> paragraph.</p><p>My <em>second</em> paragraph.</p> then the serialized result would be My first paragraph. My second paragraph. You can see the detailed description in the new working draft of Serialization 3.0.[2] [1] https://lists.w3.org/Archives/Member/w3c-xsl-query/2012Sep/0094.html (Member-only link) [2] http://www.w3.org/TR/2013/WD-xslt-xquery-serialization-30-20130108/#serdm -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 14 January 2013 10:50:34 UTC