Disco,

I imagine the problem is with #PCDATA. When including #PCDATA in a
mixed-content model, you must make sure that it is first and that you only
use '|' to separate elements and that you use only '*' and that it be used
once at the very end.

So, something like

<!ELEMENT test (#PCDATA|CODE|KEYWORD)*>
is fine

Something like

<!ELEMENT test (#PCDATA|CODE+|KEYWORD)*>
is not

So, I'm guessing that the '*'s in your flow entity are causing a problem.
Also, if you use ',' or have embedded groups within block, then you'll have
problems.

I hope that helps,

Richard.

-----Original Message-----
From: owner-xsl-list@xxxxxxxxxxxxxxxx
[mailto:owner-xsl-list@xxxxxxxxxxxxxxxx]On Behalf Of disco
Sent: Sunday, November 21, 1999 5:57 PM
To: xsl-list@xxxxxxxxxxxxxxxx
Subject: Re: XSLT choking on DTD?


It might be useful to know:

<!ENTITY % inline "#PCDATA | %fontstyle; | %phrase; | %special;">

I think the problem is surrounding the PCDATA...

Dan

On Sun, 21 Nov 1999, disco wrote:

> Hi,
>
> I'm having a strange problem: XSLT (both XT and LotusXSL) are choking on a
> part of my DTD:
>
> <!ENTITY % flow "(%inline;)* | (%block;)*">
> ...
> <!ELEMENT footnote (%flow;)>
>
> Note that inline and block are properly defined earlier in the DTD, and
> are just fine as far as all elements which use them directly are
> concerned.
>
> I have tried manually replacing "%flow;" with its expansion, unfortunately
> to no avail. Regardless of what I do, XSLT gripes that I'm missing a '('
> somewhere.
>
> Any ideas what could be going on here?
>
> Thanks,
> Dan
>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list