public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Norman Walsh <norm@berkshire.net>
To: Andrew Payne <andrew@surfnet.demon.co.uk>
Cc: docbook-tools-discuss@sources.redhat.com
Subject: Re: Tables of contents
Date: Wed, 27 Dec 2000 06:36:00 -0000	[thread overview]
Message-ID: <87g0mafc0k.fsf@nwalsh.com> (raw)
In-Reply-To: <200010060821.JAA08760@surfnet.demon.co.uk>

/ Andrew Payne <andrew@surfnet.demon.co.uk> was heard to say:
| 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?

Most users allow the stylsheets to generate TOCs automatically.
It's possible that there's a bug in manually generated TOCs, but
can you explain why you need or want to generate the TOC manually?

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <norm@berkshire.net>  | Some people tell you you should
                                   | not drink claret after
                                   | strawberries. They are
                                   | wrong.--William Maginn

WARNING: multiple messages have this Message-ID
From: Norman Walsh <norm@berkshire.net>
To: Andrew Payne <andrew@surfnet.demon.co.uk>
Cc: docbook-tools-discuss@sources.redhat.com
Subject: Re: Tables of contents
Date: Fri, 06 Oct 2000 04:26:00 -0000	[thread overview]
Message-ID: <87g0mafc0k.fsf@nwalsh.com> (raw)
Message-ID: <20001006042600.sYfcwIhAQAWXhkf_tca4i9gqIr17WMshP4xNTsRxWyc@z> (raw)
In-Reply-To: <200010060821.JAA08760@surfnet.demon.co.uk>

/ Andrew Payne <andrew@surfnet.demon.co.uk> was heard to say:
| 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?

Most users allow the stylsheets to generate TOCs automatically.
It's possible that there's a bug in manually generated TOCs, but
can you explain why you need or want to generate the TOC manually?

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <norm@berkshire.net>  | Some people tell you you should
                                   | not drink claret after
                                   | strawberries. They are
                                   | wrong.--William Maginn

  parent reply	other threads:[~2000-12-27  6:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-27  6:36 Andrew Payne
2000-10-06  1:30 ` Andrew Payne
2000-12-27  6:36 ` Norman Walsh [this message]
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=87g0mafc0k.fsf@nwalsh.com \
    --to=norm@berkshire.net \
    --cc=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).