public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Wookey <wookey@aleph1.co.uk>
To: Herman Bruyninckx <Herman.Bruyninckx@mech.kuleuven.ac.be>
Cc: docbook-tools-discuss@sources.redhat.com
Subject: Re: Best way to create an index?
Date: Tue, 18 Nov 2003 13:16:00 -0000	[thread overview]
Message-ID: <20031118131606.GC23532@knossos.aleph1.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0311171940560.13687-100000@srv04.mech.kuleuven.ac.be>

+++ Herman Bruyninckx [03-11-17 20:04 +0100]:
> I have a (steadily growing) number of docbook manuals, but haven't
> been able to generate an index for them. I have the 
> <indexterm> ... </indexterm>
> tags in the documents, but don't know how to process them :-)

me too :-)

I managed to produce an index for the HTML versions of my docs (using
collateindex.pl) but never got it to work properly for the PDF versions. I
can generate an index but most of the page numbers don't get filled in and
many that do are wrong.

It seems that changing from SGML to XML toolchains is now deemed a good
idea. Does anyone know if this will improve the index-generation for printed
docs?

herman. The answer I was given to this question a couple of years ago was
'find a script called collateindex.pl and follow the instructions in it'. As
I say, this 'mostly' worked but not well enough to produce publishable (on
paper) indexes. Good docs on the subject seem remarkably hard to come by
given what a common problem it must be.

Wookey
-- 
Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK  Tel +44 (0) 1223 811679
work: http://www.aleph1.co.uk/     play: http://www.chaos.org.uk/~wookey/

  reply	other threads:[~2003-11-18 13:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-17 19:04 Herman Bruyninckx
2003-11-18 13:16 ` Wookey [this message]
2003-11-24 18:17   ` Bob Stayton

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=20031118131606.GC23532@knossos.aleph1.co.uk \
    --to=wookey@aleph1.co.uk \
    --cc=Herman.Bruyninckx@mech.kuleuven.ac.be \
    --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).