From: Peter Toft <pto@sslug.dk>
To: docbook-tools-discuss@sources.redhat.com
Subject: Any luck with DocBook/SGML 3.1 with Red Hat 7.3?
Date: Sun, 30 Jun 2002 13:21:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0206302135540.1375-100000@ven.sslug> (raw)
Message-ID: <20020630132100.VRkLQqfy9H7yC9G2NN51PkJxX0n2jVIiRbAzLr5TtpY@z> (raw)
I try to build from DocBook/SGML 3.1-sources on Red Hat
7.3
1) When I go for HTML-output with Red Hat 6.2 or 7.2
my HTML-files would be named after the tags
"TAG-NAME" I added to my sections:
e.g. <sectN id="TAG-NAME">
Now with RH 7.3 all of my outputfile from running
docbook2html are named x1346.html and alike - not
install.html, introduction.html.
2) When I try to make PDF-output I need to run
jade to give input to the subsequent
index-collection
( perl ./collateindex.pl -g -o stikord.sgml tempdir/HTML.index)
I get lots of errors now with Red Hat 7.3 when I run
jade -t sgml -ihtml \
-d /usr/share/sgml/docbook/utils-0.6.9/docbook-utils.dsl#print \
-V html-index -V nochunks bog.sgml > ged.html
jade:/usr/share/sgml/docbook/utils-0.6.9/docbook-utils.dsl:422:19:E:
reference to undefined variable "%admon-font-family%"
jade:/usr/share/sgml/docbook/utils-0.6.9/docbook-utils.dsl:416:7:E:
reference to undefined variable "HSIZE"
jade:/usr/share/sgml/docbook/utils-0.6.9/docbook-utils.dsl:478:2:E:
too many arguments for function
jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.76/html/dbhtml.dsl:326:17:E:
invalid value for "attributes" characteristic
The last error is repeated a zillion times :))
I am not a world champion in the style-sheets - so I
could use some help along the way here.
FYI - my Docbook-header looks something like
<!doctype book PUBLIC "-//OASIS//DTD DocBook V3.1//EN" []>
And I start my books with
<book id="index" lang="da">
Any help is highly appeciated.
FYI; I run http://www.sslug.dk/linuxbog - with 13 books
in Danish with more that 1400 pages. All in
SGML/DocBook :)))))))
--
Peter Toft, Ph.D. [pto@sslug.dk] http://www.sslug.dk/~pto
The number of UNIX installations has grown to 10, with more expected
- The Unix Programmer's Manual, 2nd Edition, June 1972
next reply other threads:[~2002-06-30 20:21 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-20 19:23 Peter Toft [this message]
2002-06-30 13:21 ` Peter Toft
2002-12-20 19:23 ` Tim Waugh
2002-06-30 14:02 ` Tim Waugh
2002-12-20 19:23 ` Peter Toft
2002-07-01 14:22 ` Peter Toft
2002-12-20 19:23 ` Norman Walsh
2002-07-02 3:55 ` Norman Walsh
2002-12-20 19:23 ` Peter Toft
2002-07-02 13:48 ` Peter Toft
2002-12-20 19:23 ` Hugo van der Kooij
2002-07-03 13:59 ` Hugo van der Kooij
2002-12-20 19:23 ` Peter Toft
2002-07-03 14:01 ` Peter Toft
2002-12-20 19:23 ` Tim Waugh
2002-07-02 15:17 ` Tim Waugh
2002-12-20 19:23 ` Peter Toft
2002-07-03 13:50 ` Peter Toft
2002-12-20 19:23 ` Hugo van der Kooij
2002-07-03 14:04 ` Hugo van der Kooij
2002-12-20 19:23 ` Tim Waugh
2002-07-03 14:52 ` Tim Waugh
2002-12-20 19:23 ` Éric Bischoff
2002-07-03 21:16 ` Éric Bischoff
2002-12-20 19:23 ` Tim Waugh
2002-07-03 23:33 ` Tim Waugh
2002-12-20 19:23 ` Éric Bischoff
2002-07-04 2:51 ` Éric Bischoff
2002-12-20 19:23 ` Éric Bischoff
2002-07-01 0:49 ` Éric Bischoff
2002-12-20 19:23 ` Eric S. Raymond
2002-07-03 0:19 ` Eric S. Raymond
2002-12-20 19:23 ` Tim Waugh
2002-07-01 1:13 ` Tim Waugh
2002-12-20 19:23 ` Ismael Olea
2002-07-03 4:07 ` Ismael Olea
2002-12-20 19:23 ` Tim Waugh
2002-07-03 4:59 ` Tim Waugh
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=Pine.LNX.4.44.0206302135540.1375-100000@ven.sslug \
--to=pto@sslug.dk \
--cc=docbook-tools-discuss@sources.redhat.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).