Re: XML vers. CALS table

Subject: Re: XML vers. CALS table
From: Norman Walsh <ndw@xxxxxxxxxx>
Date: Mon, 19 Oct 1998 14:53:20 -0400
| ... <conventions><simple-content>
| <p>This manual uses the following conventions for syntax:</p>
| <table frame="all"><tgroup cols="2" colsep="1" rowsep="1">
| <colspec colwidth="88*"/>
| <colspec colwidth="308*"/><tbody ...
| When tying to convert this using jade and a DSSSL stylesheet
| jade reports an error " character data is not allowed here "
| referring to the '/' behind '"88*"'. 
| I have two questions :
| 1. What is wrong with <colspec colwidth="88*"/> ?

It's in XML and my guess is that you're using an SGML declaration.
Try passing in an XML declaration...

| 2. Why are there no complaints concerning
|     <colspec colwidth="308*"/> ?

Hmmm. Dunno.

| I admit that jade is right in complaining. My documents are in
| XML and so is the DocBook-result supposed to be. However
| I am using 'cals-tbl.elm' that is obviously a SGML-DTD, since
| it contains these '-' and 'o' bits. Thus the incriminated colspec
| is XML but however not conformant to 'cals-tbl.elm'.
| Do I only need an XML-conformant CALS table DTD ?
| If yes, where do I get it from ?

You can get a version from my DocBook XML DTD at

Norman Walsh <ndw@xxxxxxxxxx>      | Life is like arriving late for a                 | movie, having to figure out what
                                   | was going on without bothering
                                   | everybody with a lot of questions,
                                   | and then being

 DSSSList info and archive:

Current Thread