On Mon, Feb 03, 2003 at 09:49:04AM +0100, Martin van den Bemt wrote:
So maybe there should be an xml:text tag to get this handled (don't use
xslt myself though) ?
I think it's better to have a jsl:text tag that accepts the
disable-output-escaping=yes attribute. You don't need any special
xml
From: Incze Lajos [EMAIL PROTECTED]
On Mon, Feb 03, 2003 at 09:49:04AM +0100, Martin van den Bemt wrote:
So maybe there should be an xml:text tag to get this handled (don't use
xslt myself though) ?
I think it's better to have a jsl:text tag that accepts the
disable-output-escaping=yes
, February 03, 2003 8:49 AM
Subject: Re: [Jelly] Proposal new xml tag xml:entity
So maybe there should be an xml:text tag to get this handled (don't use
xslt myself though) ?
Mvgr,
Martin
On Mon, 2003-02-03 at 02:02, Incze Lajos wrote:
On Sun, Feb 02, 2003 at 03:11:53PM +0100, Martin van den Bemt
The problem is that it is not about a compliant way to do this, since I
can have any entity I define myself in my target xml (based on the DTD).
The problem is that the one that parses to the new xml file supports
everything that could end up as valid xml in the target.
Thats why I think there
On Sun, Feb 02, 2003 at 03:11:53PM +0100, Martin van den Bemt wrote:
The problem is that it is not about a compliant way to do this, since I
can have any entity I define myself in my target xml (based on the DTD).
The problem is that the one that parses to the new xml file supports
everything
Hi everyone,
Was looking at the jsl stuff in maven yesterday and one of the things
that isn't working, is using entities that are not known (logical, but
hey). Since we normally use xml to output stuff, I had an idea of adding
the xml:entity tag.
it should work like this :
xml:entity value=copy/
