On 10/01/06, Michael Kay <mike(_at_)saxonica(_dot_)com> wrote:
But if you're using saxon:parse then I'm not sure why you're also using
d-o-e...?
Thanks for having the patience to work with me on this. I was going to
write "because it seemed to be working" along with an explanation but
it was only because I was being stupid in the first place.
The actual source read "&lt;p&gt;Some random letter text
:(.&lt;/p&gt;". Don't ask me why it is double escaped. I'll
look at that some time. Anyway I remember reading that saxon doesn't
do output escaping until the final document so I didn't try value-of
for a variable. My final solution looks like:
<xsl:variable name="letter_text">
<xsl:value-of select="saxon:parse(concat('<e>', letter_text,
'</e>'))/e/child::node()" /></xsl:variable>
<xsl:copy-of select="saxon:parse(concat('<e
xmlns="http://www.w3.org/2002/06/xhtml2">',$letter_text,
'</e>'))/html:e/child::node()" />
to get around the escaped characters. I added a namespace to the
second parse just to match the namespace of the output.
The other solution would be to regex the & to & before processing
it. Sorry about taking up so much time and thank you all for your help
I wouldn't have reached a solution without it even if I had known that
my source was in a "special" format.
In future I'll read the source :).
Thank you all for all your help,
Gary
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--