From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alexander Law <exclusion@gmail.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Pg Docs <pgsql-docs@postgresql.org>
Subject: Re: <indexterm> with <secondary>
Date: Wed, 25 Oct 2017 16:23:20 -0400
Message-ID: <23010.1508963000@sss.pgh.pa.us> (raw)
In-Reply-To: <6f1a6a95-d36e-8c9e-e0d1-3e273793ad9a@gmail.com>
References: <20170315160525.42x4wxtdhk3sa522@alvherre.pgsql>
<6f1a6a95-d36e-8c9e-e0d1-3e273793ad9a@gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-docs>
Alexander Law <exclusion@gmail.com> writes:
> These duplicate entries caused by the zone attribute. If you'll remove
> it, you'll get only single entry (in secondary line).
> It seems that the following DocBook bugfix introduced the bug you
> encountered:
> https://github.com/docbook/xslt10-stylesheets/commit/f555842b> I see the following solutions for the issue:
> 1. To customize this xsl template (remove @zone check) for our docs.
> 2. To remove @zone specification from indexterm's.
> Are there any reasons to specify it explicitly?
According to my understanding, the use of "zone" means that the
indexterm entry refers to the whole section named by the "zone" label,
not only the physical point the entry is at. So I think our usage
is correct in principle; for example, this would allow an index entry
to say something like "Section 4.2" not just "page 435". In practice,
though, the distinction seems merely pedantic: AFAICS it does not
affect either HTML output (which always gives you a hyperlink to the
containing section) or PDF output (which always gives you a page number).
So we could run around and remove the zone tags, but that still seems
like rather a grotty answer --- maybe someday we'd want them back,
if the doc toolchain were ever improved to make effective use of them.
How complicated is the "customize the xsl template" solution?
(BTW, I do not see the extra-entries bug at all in PDF output.)
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, exclusion@gmail.com, alvherre@alvh.no-ip.org
Subject: Re: <indexterm> with <secondary>
In-Reply-To: <23010.1508963000@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox