The DTDDECL errors, unless I'm mistaken, can be igonored; they simply indicate that there is an SGML capability that is not implemented by OpenJade. (I'm surprised you weren't getting this message from Jade.)
However, there is also, in the installation/configuration documentation for OpenJade, a note about an additional catalog-based SYSTEM reference pointing to "builtins.dsl." The documentation says that OpenJade will not operate properly if this reference is not available. There is a catalog file in the DSSSL subdirectory of the OpenJade distribution that contains this reference; this catalog should probably be part of your catalog configuration.
To my knowledge, those are the only non-dropin aspects of OpenJade. I guess the upside is that OpenJade is more or less alive and supported while Jade is an historical artifact.
...edN
A.R. (Tom) Peters wrote:
When I process my DocBook XML file with the command: jade -t tex -V tex-backend \ -d /usr/share/sgml/docbook/stylesheet/dsssl/modular/print/docbook.dsl \ /usr/share/sgml/declaration/xml.dcl \ book.xmlThen I get reasonable output. I got the recommendation to use openjade instead. However, if I do, I get loads of messages like: openjade:/usr/share/sgml/docbook/dtd/xml/3.1.7/docbook.cat:27:0:W: DTDDECL catalog entries are not supported openjade:/usr/share/sgml/docbook/stylesheet/dsssl/modular/catalog:28:0:W: DTDDECL catalog entries are not supported So openjade is not a drop-in replacement of jade? Any caveats? What is going on, what might be wrong with DTDDECL's? -- #>!$!%(@^%#%*(&(#@#*$^@^$##*#@&(%)@**$!(&!^(#((#&%!)%*@)(&$($$%(@#)&*!^$)^@*^@) Tom "thriving on chaos" Peters NL-1062 KD nr 149 tel. +31-204080204 Amsterdam e-mail [EMAIL PROTECTED]
