docbook: Thread: Error while parsing sgml with openjade

Hi!

I try to translate an SGML-Docbook-File into Html. I installed openjade
following exactly all the steps mentioned in the "DocBook XML/SGML
Processing Using OpenJade"-HOWTO.

Unfortunately, I always get a lot of errors and I don't know what's
going wrong :-(

Here is what I get:

,----
| michael@frodo:~/isdn-howto> openjade -t sgml -i html -d
|                             /usr/local/dbtools/docbook-dsssl/html/ldp.dsl
|                             DE-Linux-ISDN-HOWTO.sgml 
| 
| /usr/local/dbtools/openjade/bin/openjade:DE-Linux-ISDN-HOWTO.sgml:292:8:E:
| document type does not allow element "PARA" here; missing one of
| "FOOTNOTE", "MSGTEXT", "CAUTION", "IMPORTANT", "NOTE", "TIP", "WARNING",
| "BLOCKQUOTE", "INFORMALEXAMPLE" start-tag
| /usr/local/dbtools/openjade/bin/openjade:DE-Linux-ISDN-HOWTO.sgml:333:9:E:
| end tag for "PARA" omitted, but OMITTAG NO was specified
| /usr/local/dbtools/openjade/bin/openjade:DE-Linux-ISDN-HOWTO.sgml:286:3:
| start tag was here
| /usr/local/dbtools/openjade/bin/openjade:DE-Linux-ISDN-HOWTO.sgml:406:8:E:
| document type does not allow element "PARA" here; missing one of
| "FOOTNOTE", "MSGTEXT", "CAUTION", "IMPORTANT", "NOTE", "TIP", "WARNING",
| "BLOCKQUOTE", "INFORMALEXAMPLE" start-tag
| /usr/local/dbtools/openjade/bin/openjade:DE-Linux-ISDN-HOWTO.sgml:415:9:E:
| end tag for "PARA" omitted, but OMITTAG NO was specified
| /usr/local/dbtools/openjade/bin/openjade:DE-Linux-ISDN-HOWTO.sgml:399:3:
| start tag was here
| /usr/local/dbtools/openjade/bin/openjade:DE-Linux-ISDN-HOWTO.sgml:604:9:E:
| document type does not allow element "ROW" here
| 
| [...] 
| 
| /usr/local/dbtools/openjade/bin/openjade:DE-Linux-ISDN-HOWTO.sgml:1057:11:E:
| end tag for "ROW" omitted, but OMITTAG NO was specified
| /usr/local/dbtools/openjade/bin/openjade:DE-Linux-ISDN-HOWTO.sgml:569:5:
| start tag was here
| 
| [...] 
`----

My document starts with:

,----
| <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V3.1//EN">
`----

And I also set the "SGML_CATALOG_FILES"-enviromentvariable as mentioned
in the Openjade-HOWTO:

,----
| michael@frodo:~/isdn-howto> echo $SGML_CATALOG_FILES
| /usr/local/dbtools/openjade/dsssl/catalog:/usr/local/dbtools/dtd3.1/docbook.cat:
| /usr/local/dbtools/docbook-dsssl/catalog
`----

Can anybody help?

Thanks,
Michael

Hello Michael, Is there is any specific why you are using SGML instead of
XML? All linux distro come with xsltproc that make it very easy to
validate content created in DocBook XML.

Moreover you can also use the online validator and transformer @
http://validate.sf.net if your content is in DocBook XML.

In Peace,
Saqib Ali
-------------
http://validate.sf.net <---- (X)HTML / DocBook Validator and Transformer

On So Mär 07, 2004, Saqib Ali ####@####.#### wrote:
> Hello Michael, Is there is any specific why you are using SGML instead of
> XML? All linux distro come with xsltproc that make it very easy to
> validate content created in DocBook XML.

I have no *really* special reason. I only choosed sgml, because I got
openjade and sgml working under W2K. Unfortunately, xml didn't work with
my config :-(

But now openjade and sgml also do not work under Linux. So no good
reason anymore to choose sgml instead of xml ;-)

> Moreover you can also use the online validator and transformer @
> http://validate.sf.net if your content is in DocBook XML.

Yes, I looked at that page yesterday. It is really useful. But I want to
have my own *working* installation. I don't know what's going wrong... I
tried to use the docbook-packages from my distribution (SuSE) as well.
No success :-(

Maybe somebody knows what's going wrong with my
openjade/docbook-installtion. I will try to use xml as well in the next
days. Maybe I have more success with it.

Bye,
Michael

Michael,

I didn't pay attention to what distro you are using, but why don't you
try this?  (I'm so behind on LDP work but had to reply to you!)

1.  Load your SGML file and change the doctype statement to the
following lines:

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">

2.  Save the file as .xml.

3.  If you have the command-line tool, run xmlproc_parse yourfile.xml
and it will give you a list of any possible errors.  You can then go
through and tweak them out.

4.  When you process with openjade, use the following syntax:

openjade -t xml -d
/usr/share/sgml/docbook/dsssl-stylesheets/html/ldp.dsl#html yourfile.xml
(that whole thing up there is all on one line, my email is wrapping.)

You should get back some decent results, as long as there are no errors
in the markup.  If you use Emacs/Xemacs with PSGML you can use a menu
command to go to the "next trouble spot" in the document if there are
any errors, and everything else can be picked up by the xmlproc_parse
command before you process it.

This is how I process all the documents I review before I send them back
to authors and it works like a charm every time.  :D

Let me know what happens.

Tab


On Sun, 2004-03-07 at 22:42, Michael Schlenstedt wrote:
> On So Mär 07, 2004, Saqib Ali ####@####.#### wrote:
> > Hello Michael, Is there is any specific why you are using SGML instead of
> > XML? All linux distro come with xsltproc that make it very easy to
> > validate content created in DocBook XML.
> 
> I have no *really* special reason. I only choosed sgml, because I got
> openjade and sgml working under W2K. Unfortunately, xml didn't work with
> my config :-(
> 
> But now openjade and sgml also do not work under Linux. So no good
> reason anymore to choose sgml instead of xml ;-)
> 
> > Moreover you can also use the online validator and transformer @
> > http://validate.sf.net if your content is in DocBook XML.
> 
> Yes, I looked at that page yesterday. It is really useful. But I want to
> have my own *working* installation. I don't know what's going wrong... I
> tried to use the docbook-packages from my distribution (SuSE) as well.
> No success :-(
> 
> Maybe somebody knows what's going wrong with my
> openjade/docbook-installtion. I will try to use xml as well in the next
> days. Maybe I have more success with it.
> 
> Bye,
> Michael
> 
> ______________________
> http://lists.tldp.org/
-- 
Tabatha Marshall
Web: www.merlinmonroe.com
Linux Documentation Project Review Coordinator (http://www.tldp.org)
Linux Counter Area Manager US:wa (http://counter.li.org)

On Mon, 2004-03-08 at 03:45, Tabatha Marshall wrote:
> 4.  When you process with openjade, use the following syntax:
> 
> openjade -t xml -d
> /usr/share/sgml/docbook/dsssl-stylesheets/html/ldp.dsl#html yourfile.xml
> (that whole thing up there is all on one line, my email is wrapping.)

Um...in case you didn't notice, you should change your paths
appropriately to the ldp.dsl.  Just wanted to make sure you didn't miss
it!


-- 
Tabatha Marshall
Web: www.merlinmonroe.com
Linux Documentation Project Review Coordinator (http://www.tldp.org)
Linux Counter Area Manager US:wa (http://counter.li.org)

* Michael Schlenstedt; ####@####.#### on 08 Mar, 2004 wrote:
>Yes, I looked at that page yesterday. It is really useful. But I want to
>have my own *working* installation. I don't know what's going wrong... I
>tried to use the docbook-packages from my distribution (SuSE) as well.
>No success :-(

have you edited /etc/profile.d/opensp.sh. Mine looks like this

# Cf. /usr/share/doc/packages/opensp/html/charset.htm
# SP_CHARSET_FIXED
# SP_SYSTEM_CHARSET
# SP_ENCODING
# SP_BCTF
export SP_USE_DOCUMENT_CATALOG=YES
export SGML_CATALOG_FILES=$HOME/sgml/CATALOG:/etc/sgml/catalog:/usr/share/sgml/CATALOG

export SP_CHARSET_FIXED=YES
export SP_ENCODING=XML
export SGML_CATALOG_FILES=$SGML_CATALOG_FILES:/usr/share/sgml/openjade/xml.soc


I have been using the SuSE packages for a long time and have not had a
problem with the docbook related packages.  
-- 

Togan Muftuoglu

Togan Muftuoglu sagte:

> have you edited /etc/profile.d/opensp.sh. Mine looks like this

Thanks, Togan, for all your hints. I've never edited the above file.
Unfortunately, I haven't access to my workstation at the moment. I will
try your hints this weekend, when I am at home again.

I will post the results to the list.

Bye and thanks,
Michael

-- 
      ___                     ####@####.####         o
     /_\ `*     `  _ ,  http://www.schlenn.net/~michael  /_\ '         ,,,
    (o o)      -  (o)o)      ICQ: 38605983 (Schlenn)    (o o) -       (o o)
ooO--(_)--Ooo--ooO'(_)--Ooo-------------------------ooO--(_)--Ooo-ooO--(_)--Ooo-

On Mo Mär 08, 2004, Tabatha Marshall ####@####.#### wrote:
> Michael,
> 
> I didn't pay attention to what distro you are using, but why don't you
> try this?  (I'm so behind on LDP work but had to reply to you!)
> 
> 1.  Load your SGML file and change the doctype statement to the
> following lines:
> 
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
> "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">

Well, there seems to be *a lot of* changes between sgml and xml?!?
Here's the result of Sagib's online-validator after I made the changes
mentioned above:

------------------------------------------------------------------------
Validating using DocBook DTD XML 4.2
This page is not Valid


Line 27, Column 11 :: element "artheader" undefined
<artheader>
-----------^
Line 275, Column 35 :: there is no attribute "LinkEnd"
mich (siehe in <xref LinkEnd="feedback">).
------------------------------^
Line 275, Column 45 :: required attribute "linkend" not specified
he in <xref LinkEnd="feedback">).
------------------------------^
Line 275, Column 46 :: end tag for "xref" omitted, but OMITTAG NO was
specified
e in <xref LinkEnd="feedback">).
------------------------------^
Line 275, Column 21 ::
an mich (siehe in <xref LinkEnd="feedback">).
---------------------^
Line 294, Column 8 :: document type does not allow element "para" here;
missing one of "footnote", "itemizedlist", "orderedlist",
"variablelist", "caution", "important", "note", "tip", "warning",
"blockquote", "informalexample" start-tag
<para>
--------^
Line 335, Column 9 :: end tag for "para" omitted, but OMITTAG NO was
specified
</sect2>
---------^
Line 288, Column 3 ::
<para>
---^
Line 408, Column 8 :: document type does not allow element "para" here;
missing one of "footnote", "itemizedlist", "orderedlist",
"variablelist", "caution", "important", "note", "tip", "warning",
"blockquote", "informalexample" start-tag
<para>
--------^
Line 414, Column 77 :: required attribute "linkend" not specified
in <xref LinkEnd="capidesign">.
------------------------------^
Line 414, Column 78 :: end tag for "xref" omitted, but OMITTAG NO was
specified
in <xref LinkEnd="capidesign">.
------------------------------^
Line 414, Column 51 ::
e unabhängig. Mehr zu CAPI in <xref LinkEnd="capidesign">.
------------------------------^
Line 417, Column 9 :: end tag for "para" omitted, but OMITTAG NO was
specified
</sect2>
---------^
Line 401, Column 3 ::
<para>
---^
Line 576, Column 9 :: document type does not allow element "row" here
<row>
---------^
Line 582, Column 9 :: document type does not allow element "row" here
<row>
---------^

[...] 

Line 1059, Column 11 :: end tag for "row" omitted, but OMITTAG NO was
specified
</tbody>
-----------^
Line 571, Column 5 ::
<row>
-----^
Line 1152, Column 23 :: required attribute "linkend" not specified
LinkEnd="capifigure"> zeigt die einzelnen Modul
-----------------------^
Line 1152, Column 24 :: end tag for "xref" omitted, but OMITTAG NO was
specified
LinkEnd="capifigure"> zeigt die einzelnen Modul
------------------------^
Line 1151, Column 63 ::
nder in Abhängigkeit stehen. <xref
------------------------------^
Line 1234, Column 81 :: required attribute "linkend" not specified
ref LinkEnd="capikernelconfig">)
------------------------------^
Line 1234, Column 82 :: end tag for "xref" omitted, but OMITTAG NO was
specified
ef LinkEnd="capikernelconfig">)
------------------------------^
Line 1234, Column 49 ::
nterstützung im Kernel (siehe <xref LinkEnd="capikernelconfig">)
------------------------------^
Line 1395, Column 30 :: there is no attribute "LinkEnd"
aktivieren. <Xref LinkEnd="capiisdnsubsystem">
------------------------------^
Line 1395, Column 49 :: element "Xref" undefined
ef LinkEnd="capiisdnsubsystem"> zeigt die benötigten
------------------------------^
Line 1398, Column 9 :: end tag for "Xref" omitted, but OMITTAG NO was
specified
</para>
---------^
Line 1395, Column 16 ::
aktivieren. <Xref LinkEnd="capiisdnsubsystem">
----------------^
Line 1436, Column 18 :: there is no attribute "LinkEnd"
(<XREF LinkEnd="capimisdnsubsystem">).
------------------^
Line 1436, Column 38 :: element "XREF" undefined
F LinkEnd="capimisdnsubsystem">).
------------------------------^
Line 1437, Column 9 :: end tag for "XREF" omitted, but OMITTAG NO was
specified
</para>
---------^
Line 1436, Column 4 ::
(<XREF LinkEnd="capimisdnsubsystem">).
----^

-----------------------------------------------------------------------


> 4.  When you process with openjade, use the following syntax:
> 
> openjade -t xml -d
> /usr/share/sgml/docbook/dsssl-stylesheets/html/ldp.dsl#html yourfile.xml
> (that whole thing up there is all on one line, my email is wrapping.)

Well, here's the result:

-----------------------------------------------------------------------
michael@frodo:~/isdn-howto/compactflash/de> /usr/bin/openjade -t xml -d
/usr/local/dbtools/docbook-dsssl/html/ldp.dsl#html DE-Linux-ISDN-HOWTO.xml
/usr/bin/openjade:<URL>http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd:112:17:E: "X20AC" is not a function name
/usr/bin/openjade:<URL>http://www.oasis-open.org/docbook/xml/4.2/ent/iso-amsa.ent:8:19:E: "X21B6" is not a function name
/usr/bin/openjade:<URL>http://www.oasis-open.org/docbook/xml/4.2/ent/iso-amsa.ent:9:19:E: "X21B7" is not a function name
/usr/bin/openjade:<URL>http://www.oasis-open.org/docbook/xml/4.2/ent/iso-amsa.ent:10:17:E: "X21D3" is not a function name

[...] 

/usr/bin/openjade:I: maximum number of errors (200) reached; change with -E option
/usr/bin/openjade:/usr/local/dbtools.old/docbook-dsssl/html/ldp.dsl:2:54:W: cannot generate system identifier for public text "-//James Clark//DTD DSSSL Style Sheet//EN"
/usr/bin/openjade:/usr/local/dbtools.old/docbook-dsssl/html/ldp.dsl:16:0:E: reference to entity "STYLE-SHEET" for which no system identifier could be generated
/usr/bin/openjade:/usr/local/dbtools.old/docbook-dsssl/html/ldp.dsl:1:0: entity was defined here
/usr/bin/openjade:/usr/local/dbtools.old/docbook-dsssl/html/ldp.dsl:16:0:E: DTD did not contain element declaration for document type name
/usr/bin/openjade:/usr/local/dbtools.old/docbook-dsssl/html/ldp.dsl:12:0:E: notation "DSSSL" for entity "docbook.dsl" undefined
/usr/bin/openjade:/usr/local/dbtools.old/docbook-dsssl/html/ldp.dsl:18:12:E: element "STYLE-SHEET" undefined
/usr/bin/openjade:/usr/local/dbtools.old/docbook-dsssl/html/ldp.dsl:40:24:E: there is no attribute "ID"
/usr/bin/openjade:/usr/local/dbtools.old/docbook-dsssl/html/ldp.dsl:40:36:E: there is no attribute "USE"
/usr/bin/openjade:/usr/local/dbtools.old/docbook-dsssl/html/ldp.dsl:40:45:E: element "STYLE-SPECIFICATION" undefined
/usr/bin/openjade:/usr/local/dbtools.old/docbook-dsssl/html/ldp.dsl:41:25:E: element "STYLE-SPECIFICATION-BODY" undefined
/usr/bin/openjade:/usr/local/dbtools.old/docbook-dsssl/html/ldp.dsl:132:44:E: element "STYLE-SPECIFICATION" undefined
/usr/bin/openjade:/usr/local/dbtools.old/docbook-dsssl/html/ldp.dsl:133:25:E: element "STYLE-SPECIFICATION-BODY" undefined
/usr/bin/openjade:/usr/local/dbtools.old/docbook-dsssl/html/ldp.dsl:362:27:E: there is no attribute "ID"
/usr/bin/openjade:/usr/local/dbtools.old/docbook-dsssl/html/ldp.dsl:362:46:E: there is no attribute "DOCUMENT"
/usr/bin/openjade:/usr/local/dbtools.old/docbook-dsssl/html/ldp.dsl:362:59:E: element "EXTERNAL-SPECIFICATION" undefined
/usr/bin/openjade:E: specification document does not have the DSSSL architecture as a base architecture
/usr/bin/openjade:E: no style-specification or external-specification with ID "HTML"
-----------------------------------------------------------------------

Bye,
Michael

On Sat, 2004-03-13 at 10:39, Michael Schlenstedt wrote:

> Well, there seems to be *a lot of* changes between sgml and xml?

XML is case-sensitive unlike SGML.

-- 
Ari Makela ####@####.####

On Sa Mär 13, 2004, Ari Makela ####@####.#### wrote:
> On Sat, 2004-03-13 at 10:39, Michael Schlenstedt wrote:
> 
> > Well, there seems to be *a lot of* changes between sgml and xml?
> 
> XML is case-sensitive unlike SGML.
> 

Ah, ok. I try to do it step-by-step now. I first try to get an validate
xml-document, after that, I will try to translate it into html ot any
other format.

So the only errors I got from the online-validator are now:

,----
| Line 277, Column 46 ::  end tag for "xref" omitted, but OMITTAG NO was
| specified
| e in <xref linkend="feedback">).
| ------------------------------^
`----

,----
| Line 586, Column 9 ::  document type does not allow element "row" here
| <row>
| ---------^
`----

Well, in sgml, xref do not need any end-tag. It just shows "Figure 5",
"Section 3" are somthing similar where I put "<xref
linkend="feedback">". Must I use somthing like that in xml?

<xref linkend="feedback"></xref>

The next point is the table I use in my document. Here I get a lot of
error like "document type does not allow element "row" here". That's the
code I use:


   <table frame='all'><title>Unterstütze Hardware (ohne Gewähr!)</title>
    <tgroup cols='4' align='left' colsep='1' rowsep='1'>
    <thead>
     <row>
      <entry>Bezeichnung</entry>
      <entry>Open Source I4L-Treiber</entry>
      <entry>Open Source CAPI-Treiber</entry>
      <entry>Eigener Hersteller-Treiber</entry>
     </row>
    </thead>
    <tbody>
     <row>
      <entry>ACER P10</entry>
      <entry>Ja</entry>
      <entry>Nein</entry>
      <entry>?</entry>
     </row>
    </tbody>
    </tgroup>
   </table>


Thanks a lot for helping,
Michael