Re: Bug fix for the style-sheet DTD.

[Chris Maden <crism@xxxxxxxxxxx>]

[Didier PH Martin]
> <!element style-specification-body o o CDATA>
> <!attlist style-specification-body
>   content entity #conref
> >
> 
> That's it, now you can include any "<>" stuff. So SGML is not so bad
> after all :-).

Except you can't include just *any* "<>" stuff.

In CDATA declared content, the </ delimiter is recognized, and it is
an error if the GI that follows is not that of a currently open
element, or if there is no GI following.  (See Annex B, clause
B.13.1.1, of ISO 8879:1986).  So there's no way, in CDATA delcared
content, to have "</" next to each other; for flexibility, #PCDATA is
the way to go.  Use a CDATA marked section in the style-specification-
body if you need to.

(I'm currently using

<!ENTITY % programlisting.content "CO | LineAnnotation | %para.char.mix;">
<!ELEMENT ProgramListing - - ((%programlisting.content;)+)>

<!ENTITY % local.programlisting.attrib
         "DSSSL   NAME               "style-specification-body"
          content ENTITY             #CONREF">
<!ATTLIST ProgramListing
		%width.attrib;
		%linespecific.attrib;
		%common.attrib;
		%programlisting.role.attrib;
		%local.programlisting.attrib;
>
)

-Chris
-- 
<!NOTATION SGML.Geek PUBLIC "-//Anonymous//NOTATION SGML Geek//EN">
<!ENTITY crism PUBLIC "-//O'Reilly//NONSGML Christopher R. Maden//EN"
"<URL>http://www.oreilly.com/people/staff/crism/ <TEL>+1.617.499.7487
<USMAIL>90 Sherman Street, Cambridge, MA 02140 USA" NDATA SGML.Geek>


 DSSSList info and archive:  http://www.mulberrytech.com/dsssl/dssslist