From: "Raj, Ashok" <ashok.raj@intel.com>
To: "'docbook-tools-discuss@sourceware.cygnus.com'"
<docbook-tools-discuss@sourceware.cygnus.com>
Subject: Help wanted ...
Date: Wed, 16 Jan 2002 16:17:00 -0000 [thread overview]
Message-ID: <8A9A5F4E6576D511B98F00508B68C20A04200243@orsmsx106.jf.intel.com> (raw)
Message-ID: <20020116161700.jxofOFWv0TKgXE8vTGmoIz9EKyAkCKRUoPNusFSoXzk@z> (raw)
Hello docbook gurus...
Iam using genrd (version of robodoc that can generate sgml docbook style
output) for API documentation.
once the sgml file is produced, iam not able to use any tools sgml2html etc
to convert this to html source files.
To check if there is anything wrong and go from basics, i tried to take an
example in
http://nis-www.lanl.gov/~rosalia/mydocs/docbook-intro.html
the output from the example is here shown below. The error output is here..
Can someone let me know what environment settings i should use. Iam having
Redhat 7.2 and all sgml related stuff is installed in /usr/share/sgml
Thanks in advance
ashokr
--- ERROR OUTPUT ------------
[root@sakthi test]# sgml2html api.sgml
Processing file api.sgml
/usr/bin/nsgmls:<OSFD>0:1:59:W: cannot generate system identifier for public
text "-//Davenport//DTD DocBook V3.0//EN"
/usr/bin/nsgmls:<OSFD>0:2:0:E: reference to entity "BOOK" for which no
system identifier could be generated
/usr/bin/nsgmls:<OSFD>0:1:0: entity was defined here
/usr/bin/nsgmls:<OSFD>0:2:0:E: DTD did not contain element declaration for
document type name
/usr/bin/nsgmls:<OSFD>0:3:5:E: element "BOOK" undefined
/usr/bin/nsgmls:<OSFD>0:4:11:E: element "BOOKINFO" undefined
/usr/bin/nsgmls:<OSFD>0:5:9:E: element "DATE" undefined
/usr/bin/nsgmls:<OSFD>0:6:10:E: element "TITLE" undefined
/usr/bin/nsgmls:<OSFD>0:7:13:E: element "SUBTITLE" undefined
/usr/bin/nsgmls:<OSFD>0:9:6:E: element "TOC" undefined
/usr/bin/nsgmls:<OSFD>0:12:10:E: element "CHAPTER" undefined
/usr/bin/nsgmls:<OSFD>0:13:10:E: element "TITLE" undefined
/usr/bin/nsgmls:<OSFD>0:14:9:E: element "PARA" undefined
/usr/bin/nsgmls:<OSFD>0:16:10:E: element "SECT1" undefined
/usr/bin/nsgmls:<OSFD>0:17:12:E: element "TITLE" undefined
/usr/bin/nsgmls:<OSFD>0:18:11:E: element "PARA" undefined
/usr/bin/nsgmls:<OSFD>0:22:11:E: element "APPENDIX" undefined
/usr/bin/nsgmls:<OSFD>0:23:10:E: element "TITLE" undefined
/usr/bin/nsgmls:<OSFD>0:24:9:E: element "PARA" undefined
/usr/bin/nsgmls:<OSFD>0:26:10:E: element "SECT1" undefined
/usr/bin/nsgmls:<OSFD>0:27:12:E: element "TITLE" undefined
/usr/bin/nsgmls:<OSFD>0:28:11:E: element "PARA" undefined
/usr/bin/nsgmls:<OSFD>0:29:17:E: element "EMPHASIS" undefined
/usr/bin/sgmlsasp: can't open `/usr/lib/sgml-tools/dist/book/html/mapping':
No such file or directory
--- SOURCE FILE ------------
[root@sakthi test]# cat api.sgml
<!doctype book PUBLIC "-//Davenport//DTD DocBook V3.0//EN" [
]>
<book>
<bookinfo>
<date>1997-10-11</date>
<title>My first booklet</title>
<subtitle>it even has a subtitle</subtitle>
</bookinfo>
<toc></toc>
<!-- We are done with the preliminaries, now we can start with
the body of the document -->
<chapter>
<title>My first chapter</title>
<para>Here's a paragraph of text because it is stylistically
poor to start a section right after the chapter title.</para>
<sect1>
<title>A section in that first chapter</title>
<para>All I need is a single paragraph of text to make the
section valid.</para>
</sect1>
</chapter>
<appendix>
<title>Remaining details</title>
<para>Although this booklet is quite complete, here I will
mention some details I never got to.</para>
<sect1>
<title>Use of the word dude</title>
<para>Here's an example of how to say
<emphasis>dude</emphasis>: DUDE.</para>
</sect1>
</appendix>
</book>
next reply other threads:[~2002-01-17 0:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-20 19:23 Raj, Ashok [this message]
2002-01-16 16:17 ` Raj, Ashok
2002-12-20 19:23 ` Tim Waugh
2002-01-17 2:00 ` Tim Waugh
2002-12-20 19:23 ` Éric Bischoff
2002-01-17 2:11 ` Éric Bischoff
2002-12-20 19:23 ` Éric Bischoff
2002-01-17 1:18 ` Éric Bischoff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8A9A5F4E6576D511B98F00508B68C20A04200243@orsmsx106.jf.intel.com \
--to=ashok.raj@intel.com \
--cc=docbook-tools-discuss@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).