From: Peter Eisentraut <peter_e@gmx.net>
To: Daniele Varrazzo <daniele.varrazzo@gmail.com>
Cc: pgsql-docs@postgresql.org
Subject: Re: Please provide stable target anchors
Date: Thu, 08 Jul 2010 21:09:50 +0300
Message-ID: <1278612590.25038.2.camel@vanquo.pezone.net> (raw)
In-Reply-To: <AANLkTikAgIyYfwy_2Zj8GafoC7ZFlGv5iCdab1l7VuDp@mail.gmail.com>
References: <AANLkTikAgIyYfwy_2Zj8GafoC7ZFlGv5iCdab1l7VuDp@mail.gmail.com>
On tor, 2010-07-08 at 15:54 +0100, Daniele Varrazzo wrote:
> In psycopg documentation I've often referenced specific parts of
> PostgreSQL docs, e.g. libpq functions, using the anchors found in the
> html docs (see [1] for example). Unfortunately these anchors are not
> stable and the ones I've linked to have changed, leaving half-broken
> links referring to the correct page but to not existing fragments ([2]
> for the example above).
If you can tell us which places you want to link to, we can make stable
anchors.
> The html anchors seem generated from the <indexterm> tags in the sgml
> documentation. Would it be possible to generate stable anchors for
> these targets, e.g. "slugifying" the content of the <primary> tag
> contained in them?
No, the anchors are made from the id attributes. But if there is no id
attribute, the toolchain generates an identifier for the anchor, which
is some number that is obviously not stable. The fix is then to put
id's into these places.
> Uhm... looking at the currently published html doc, it seems there is
> a problem: the index [3] doesn't use these anchors at all. See for
> example the entries for any libpq function.
I'm not sure I'm seeing what you're seeing. Could you provide examples?
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: peter_e@gmx.net, daniele.varrazzo@gmail.com
Subject: Re: Please provide stable target anchors
In-Reply-To: <1278612590.25038.2.camel@vanquo.pezone.net>
* 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