W3C home > Mailing lists > Public > public-qt-comments@w3.org > September 2016

[Bug 29831] New: [FO31] fn:transform and serialization to string

From: <bugzilla@jessica.w3.org>
Date: Tue, 20 Sep 2016 12:59:27 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29831-523@http.www.w3.org/Bugs/Public/>

            Bug ID: 29831
           Summary: [FO31] fn:transform and serialization to string
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Functions and Operators 3.1
          Assignee: mike@saxonica.com
          Reporter: abel.braaksma@xs4all.nl
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

When serializing to a string, what serialization-options are applicable? And in
the case of a 1.0 processor, does disable-output-escaping come into play
(provided a processor supports it)?


<xsl:value-of select="'&lt;br>'" disable-output-escaping="true" />

The output would be "<br>".

and: <xsl:value-of select="'&lt;br>'" disable-output-escaping="false" />

The output would be "&lt;br>"

Does the returned string contain '<', 'b', 'r', '>' ("<br>", and therefore
illegal XML), or does the string contain '&', 'l', 't', ';' , 'b', 'r', '>'
("&lt;br>" and therefore legal XML)?

And with respect to other output options:
- if non-UTF is specified, do we return expanded entities?
- if character-maps is specified, are they invoked (leading, again, to
potentially illegal XML)
- if HTML is specified, do we return the string for HTML, or a parsable XML

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 20 September 2016 12:59:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:58:02 UTC