The transformation engine is .Net's XSLTCompiledTransform on the
backend, so I should be fine! I don't need a cross-platform solution
for this one.
Karl.
On Mon, Oct 1, 2012 at 8:58 AM, David Carlisle
<davidc(_at_)nag(_dot_)co(_dot_)uk> wrote:
On 01/10/2012 16:46, Karl Stubsjoen wrote:
Wow. I didn't think that worked like that. Cool, thanks.
It only works like that where d-o-e is supported but it is explicitly an
optional feature, notably mozilla doesn't support it as it generates a dom
directly rather than producing serialised output, so it isn't doing any
escaping that needs disabling.
A more robust solution if it is available is to parse the string (using an
extension function such as saxon:parse) or the parser being proposed for
xslt 3 or a parser written in XSLT.
David
--
google plus: https:/profiles.google.com/d.p.carlisle
________________________________________________________________________
The Numerical Algorithms Group Ltd is a company registered in England
and Wales with company number 1249803. The registered office is:
Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.
This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs.
________________________________________________________________________
--
Karl Stubsjoen
MeetScoresOnline.com
(602) 845-0006
--~------------------------------------------------------------------
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>
--~--