[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
RE: xt and jade
Subject: RE: xt and jade From: Linda van den Brink <lvdbrink@xxxxxxx> Date: Fri, 15 Oct 1999 14:14:36 +0200 |
Both behaviours are right. In XML, <tag></tag> and <tag/> are exactly the same. I don't think you can force either of these XSL processors to behave other than they do by default (I'm not completely sure). To avoid your problem with Jade, can't you feed it the xml decl so that it accepts the <tag/> form? -----Original Message----- From: pietro abate [mailto:pietro.abate@xxxxxx] Sent: Friday, October 15, 1999 12:43 PM To: xsl Subject: xt and jade Hi, I've seen that xt and saxon have two different behavior with the empty tags. If in my xsl there is a samething like <tag></tag> saxon copies the two tags, but xt write the short form <tag/>... If I try to generate an sgml file after jade didn't want work because the sgml decl forbid the second form. which is the right behavior, and how can I force xt to work like saxon ? TIA, pietro XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
xt and jade, pietro abate | Thread | replacing characters in a string, Linda van den Brink |
replacing characters in a string, Linda van den Brink | Date | Re: replacing characters in a strin, David Carlisle |
Month |