On Mon, 24 Mar 2014 20:12:50 +
Graeme Geldenhuys wrote:
>[...]
> > The parser converts &#*; to Unicode characters when
> > reading. AFAIR some xsl parsers like xsltproc do the same.
> > If you want xslt to output ' ' you can use ' '
>
> Thanks for that info, it helped find the problem (
On 2014-03-24 13:58, Mattias Gaertner wrote:
>
> Yes, XSL is XML.
Thought so - thanks for confirming.
> The parser converts &#*; to Unicode characters when
> reading. AFAIR some xsl parsers like xsltproc do the same.
> If you want xslt to output ' ' you can use ' '
Thanks for that info, i
On Sun, 23 Mar 2014 17:58:16 +
Graeme Geldenhuys wrote:
> Hi,
>
> I'm loading up a XSL file into a TXMLDocument using XMLRead. Up to this
> point everything seems to be ok, and I can query the DOMNodes without
> problem. If I then save that file out again, using XMLWrite, I noticed
> that so
On Sun, Mar 23, 2014 at 2:58 PM, Graeme Geldenhuys
wrote:
> I'm using FPC 2.6.2 under 64-bit FreeBSD, but will be compiling this
> application for Windows 32-bit and 64-bit tomorrow at work.
If you can, try also the "Laz2_" XML units: Laz2_Dom, Laz2_xmlwrite and read.
They seem to work better wi
Hi,
I'm loading up a XSL file into a TXMLDocument using XMLRead. Up to this
point everything seems to be ok, and I can query the DOMNodes without
problem. If I then save that file out again, using XMLWrite, I noticed
that some data is lost. :-/
I don't know if this is because the file is a XSL fi
