This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: illegal elements must go...
- To: xsl-list at mulberrytech dot com
- Subject: Re: illegal elements must go...
- From: Gary L Peskin <garyp at firstech dot com>
- Date: Fri, 25 Aug 2000 09:48:38 -0700
- Organization: The Firstech Corporation
- References: <3.0.6.32.20000825125316.01233980@NTServer>
- Reply-To: xsl-list at mulberrytech dot com
Jeni Tennison wrote:
>
> Jukka,
>
> >I'm having parent element which can have many childrens (in source). But the
> >result side (in DTD) there are fewer possible elements. So, solution I'm
> >gonna do is to put those 'illegal' (in result side) elements childrens of
> >para element(s).
>[snip]
> This works in SAXON. It doesn't work in Xalan, which ignores the illegal
> nodes that occur at the end of the 'entry': either Xalan doesn't produce an
> empty string when generate-id() is called on an empty node set, or it
> doesn't like having key values that are empty strings.
This works fine in the current version of Xalan (1.2.D02). I just
tested it.
Gary
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list