public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Payne <andrew@surfnet.demon.co.uk>
To: docbook-tools-discuss@sources.redhat.com
Subject: Tables of contents
Date: Fri, 06 Oct 2000 01:30:00 -0000	[thread overview]
Message-ID: <200010060821.JAA08760@surfnet.demon.co.uk> (raw)
Message-ID: <20001006013000.dxSk5oiuJIMptpmVjb6-OLouHmApbhzpQx7OlpBIVy4@z> (raw)

Hi.

I'm having immense trouble getting docbook2rtf to correctly fill in
page numbers in TOCENTRYs.

If I run docbook2dvi three times (!) then it usually does fill in the
numbers, but insists on underlining every entry which looks terrible.

docbook2rtf, who's output is generally good, completely refuses to
and shows all page numbers as being '1'.

Does anyone have a reliable way of producing TOCs with these tools?

Here's my SGML snippet.  I tried playing with XREF and LINK to see
if they helped, which they didn't.

<toc>
<tocpart>
	<tocentry linkend='partvisp'></tocentry>
	<tocchap>
		<tocentry linkend='chapvispsystemoverview'></tocentry>
		<toclevel1>
			<tocentry linkend='sectvispoverviewinventory'></tocentry>
		</toclevel1>
	</tocchap>
</tocpart>
<tocpart>
	<tocentry linkend='partinternal'></tocentry>
	<tocchap>
		<tocentry linkend='chapintoverview'></tocentry>
	</tocchap>
	<tocchap>
		<tocentry>
		<xref linkend='chapintfirewall'>
		</tocentry>
	</tocchap>
</tocpart>
</toc>



Andrew.

             reply	other threads:[~2000-10-06  1:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-27  6:36 Andrew Payne [this message]
2000-10-06  1:30 ` Andrew Payne
2000-12-27  6:36 ` Norman Walsh
2000-10-06  4:26   ` Norman Walsh
2000-12-27  6:36   ` Andrew Payne
2000-10-06  4:35     ` Andrew Payne
2000-12-27  6:36     ` Norman Walsh
2000-10-06  5:13       ` Norman Walsh

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=200010060821.JAA08760@surfnet.demon.co.uk \
    --to=andrew@surfnet.demon.co.uk \
    --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).