Rob Posted May 13, 2020 Share Posted May 13, 2020 I'm using XSLT to take XML and output to different XML. One node has <pronounce>ă-būs′ dē-t&ebreve;r′&ebreve;nt</pronounce> This <xsl:value-of select="$storage/mainentry/pronounce[1]" disable-output-escaping="yes"/> Only outputs -bs d-trnt but I want it to output exactly what's in the document: ă-būs′ dē-t&ebreve;r′&ebreve;nt Link to comment Share on other sites More sharing options...
Ingolme Posted May 13, 2020 Share Posted May 13, 2020 In XML, those would be considered invalid entities, though it is valid if the document is HTML. You can escape them by turning every & into & <pronounce>&abreve;-b&umacr;s&prime; d&emacr;-t&ebreve;ramp;′&ebreve;nt</pronounce> Doing this straight through XSLT, I'm not certain, but you might want to set disable-output-escaping to "no" so that it will escape the characters. Link to comment Share on other sites More sharing options...
Rob Posted May 13, 2020 Author Share Posted May 13, 2020 That was submitted prematurely. Allow me to restate: I'm using XSLT to take XML and output to different XML. One node has <pronounce>ă-būs′ dē-t&ebreve;r′&ebreve;nt</pronounce> This <xsl:value-of select="$storage/mainentry/pronounce[1]" disable-output-escaping="yes"/> Only outputs -bs d-trnt but I want it to output exactly what's in the document: ă-būs′ dē-t&ebreve;r′&ebreve;nt Or even transform the entities to the HTML equivalents. Those entities are not declared in the document. Is there a way to add a declaration to the style sheet? I cannot add the declaration to each of the thousands of documents. Many thanks. Link to comment Share on other sites More sharing options...
Ingolme Posted May 13, 2020 Share Posted May 13, 2020 Did you try changing the value of "disable-output-escaping"? Link to comment Share on other sites More sharing options...
Rob Posted May 13, 2020 Author Share Posted May 13, 2020 Sorry, yes, here's all of the methods I've tried: <pronounce><xsl:value-of select="$storage/mainentry/pronounce[1]/text()" disable-output-escaping="yes"/></pronounce><br/> <pronounce><xsl:value-of select="$storage/mainentry/pronounce[1]/text()" disable-output-escaping="no"/></pronounce> <pronounce><xsl:value-of select="$storage/mainentry/pronounce" disable-output-escaping="yes"/></pronounce> <pronounce><xsl:value-of select="$storage/mainentry/pronounce" disable-output-escaping="no"/></pronounce> <pronounce><xsl:value-of select="$storage/mainentry/pronounce[1]" disable-output-escaping="yes"/></pronounce> <pronounce><xsl:value-of select="$storage/mainentry/pronounce[1]" disable-output-escaping="no"/></pronounce> The all produce same result: <pronounce>-bs d-trnt</pronounce> <pronounce>-bs d-trnt</pronounce> <pronounce>-bs d-trnt</pronounce> <pronounce>-bs d-trnt</pronounce> <pronounce>-bs d-trnt</pronounce> Link to comment Share on other sites More sharing options...
Ingolme Posted May 13, 2020 Share Posted May 13, 2020 I tried to test this in the browser but it rejected the XML because of undefined entities. Which XSLT engine are you using? It looks like your XSLT engine is allowing it to run but stripping out entities that it does not understand. Link to comment Share on other sites More sharing options...
Rob Posted May 13, 2020 Author Share Posted May 13, 2020 That is what's happening. It uses a custom-bulit engine. This is how the $storage variable is being created: <xsl:copy-of select="doc(concat('c:///service/assets/asset/id/', asset/@id, '/version/', asset/@version, '/storage/master/file'))"/> Is there a better way to do that so that it wouldn't do this? Link to comment Share on other sites More sharing options...
Rob Posted May 13, 2020 Author Share Posted May 13, 2020 If I add this to the source file it works: <!DOCTYPE mainentry [ <!ENTITY abreve "&#x0103;"> ]> I get proper output of ă However, I cannot add that to all of the files. Is there something I can do in the XSLT to accomplish this? Somehow insert that and other entity declarations either into the doc or with an include of somekind? Link to comment Share on other sites More sharing options...
Ingolme Posted May 13, 2020 Share Posted May 13, 2020 XSLT can only deal with valid XML. If you have another programming language available to you, you could have it replace the entities before sending the XML to the XSLT engine. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now