[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Asymmetric string handling with processing-instruction

Subject: Asymmetric string handling with processing-instructions
From: "Michael Mueller-Hillebrand michael.mueller-hillebrand@xxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 14 Sep 2023 14:05:32 -0000
 Asymmetric string handling with processing-instruction
Dear colleagues,

We are (finally) switching to Saxon 10 (shame on us for being so late) and
experience the breaking change in the very welcome extension function
saxon:get-pseudo-attribute(). The change history states:

B7        The extension function saxon:get-pseudo-attribute() now parses the
supplied input much more rigorously, applying the rules found in the W3C
specification<https://www.w3.org/TR/2010/REC-xml-stylesheet-20101028/>, and
raising an error for invalid syntax that was previously allowed through.

Check out this example which changes <p> into PI and vice versa:
    <p>Marks &amp; Spencer Text</p>
    <?my value="Marks &amp; Spencer PI"?>

<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="3.0"

    <xsl:mode on-no-match="shallow-copy"/>
    <xsl:output method="xml" indent="yes"/>

    <xsl:template match="p">
        <xsl:processing-instruction name="my" select="'value=&quot;' ||
string(.) || '&quot;'"/>

    <xsl:template match="processing-instruction(my)">
            <xsl:text>String: </xsl:text>
            <xsl:value-of select="string(.)"/>
            <xsl:text>s:g-p-a: </xsl:text>
            <xsl:value-of select="./saxon:get-pseudo-attribute('value')"/>

The result with Saxon 10+ is:
   <?my value="Marks & Spencer Text"?>
   <p>String: value="Marks &amp;amp; Spencer PI"</p>
   <p>s:g-p-a: Marks &amp; Spencer PI</p>

The PI in the result shows the part of the spec which says: bNote that
special characters occurring within the PI text will not be escaped.b

My bottom line: If you want to use saxon:get-pseudo-attribute(), because it is
elegant and efficient, and it could be possible you have user content in
processing instruction, you have two additional tasks:
* When using xsl:processing-instruction or other ways to create processing
instructions, make sure to escape the five XML characters
* When accessing PI string values without saxon:get-pseudo-attribute, add an
unescaping routine to avoid double escaped content.

How do you deal with this asymmetry?

Best regards
- Michael

Michael MC<ller-Hillebrand
Senior Consultant
Phone +49 951-20859-752
Mobil +49 172-819 34 13
www.docufy.de<https://www.docufy.de/> |
DOCUFY GmbH | KirschC$ckerstr. 27 | 96052 Bamberg | Deutschland
CEO: Nadine Prill | Amtsgericht Bamberg HRB10571

Current Thread


Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.