public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Bob Stayton <bobs@sco.com>
To: Wookey <wookey@aleph1.co.uk>
Cc: Herman Bruyninckx <Herman.Bruyninckx@mech.kuleuven.ac.be>,
	docbook-tools-discuss@sources.redhat.com
Subject: Re: Best way to create an index?
Date: Mon, 24 Nov 2003 18:17:00 -0000	[thread overview]
Message-ID: <20031124093545.F22425@sco.com> (raw)
In-Reply-To: <20031118131606.GC23532@knossos.aleph1.co.uk>; from wookey@aleph1.co.uk on Tue, Nov 18, 2003 at 01:16:07PM +0000

On Tue, Nov 18, 2003 at 01:16:07PM +0000, Wookey wrote:
> +++ 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?

If you process your XML with the DSSSL tools, then you
still must use the collateindex.pl step.  If you use
the XSL stylesheets and tools, then the stylesheet will
generate the index automatically if you have an empty
<index/> element in your document.  I consider that
a big improvement.  However, the current version of FOP,
the major free FO processor, does not know how to
collapse duplicate page references and page ranges in
an index.  The XEP processor can do that, though.

-- 

Bob Stayton                                 400 Encinal Street
Publications Architect                      Santa Cruz, CA  95060
Technical Publications                      voice: (831) 427-7796
The SCO Group                               fax:   (831) 429-1887
                                            email: bobs@sco.com

      reply	other threads:[~2003-11-24 18:17 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
2003-11-24 18:17   ` Bob Stayton [this message]

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=20031124093545.F22425@sco.com \
    --to=bobs@sco.com \
    --cc=Herman.Bruyninckx@mech.kuleuven.ac.be \
    --cc=docbook-tools-discuss@sources.redhat.com \
    --cc=wookey@aleph1.co.uk \
    /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).