From: Norman Walsh <ndw@nwalsh.com>
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: <87og0ydvad.fsf@nwalsh.com> (raw)
In-Reply-To: <200010061126.MAA09777@surfnet.demon.co.uk>
/ Andrew Payne <andrew@surfnet.demon.co.uk> was heard to say:
| > 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?
|
| I tried this - and it did the all-pages-are-1 thing - so I tried
| doing manual entries to see if anything improved.
In the RTF, you have to load the document in Word or some other program
and ask it to regen the numbers. This is described in the Jade document
at http://www.jclark.com/jade/#backend-rtf , have you tried that?
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | People say law but they mean
http://nwalsh.com/ | wealth.--Emerson
WARNING: multiple messages have this Message-ID
From: Norman Walsh <ndw@nwalsh.com>
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 05:13:00 -0000 [thread overview]
Message-ID: <87og0ydvad.fsf@nwalsh.com> (raw)
Message-ID: <20001006051300.Ag3awLfH2ViZR4Exocxn10nBeqivuKM4i0AMq6XE3rw@z> (raw)
In-Reply-To: <200010061126.MAA09777@surfnet.demon.co.uk>
/ Andrew Payne <andrew@surfnet.demon.co.uk> was heard to say:
| > 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?
|
| I tried this - and it did the all-pages-are-1 thing - so I tried
| doing manual entries to see if anything improved.
In the RTF, you have to load the document in Word or some other program
and ask it to regen the numbers. This is described in the Jade document
at http://www.jclark.com/jade/#backend-rtf , have you tried that?
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | People say law but they mean
http://nwalsh.com/ | wealth.--Emerson
next prev 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
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 [this message]
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=87og0ydvad.fsf@nwalsh.com \
--to=ndw@nwalsh.com \
--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).