This is the mail archive of the
docbook-apps@lists.oasis-open.org
mailing list .
Re: website: feature request
- From: Bob Stayton <bobs at caldera dot com>
- To: Dave Pawson <davep at dpawson dot freeserve dot co dot uk>,docbook-apps at lists dot oasis-open dot org
- Date: Sun, 05 May 2002 00:42:37 -0700
- Subject: Re: DOCBOOK-APPS: website: feature request
- References: <5.1.0.14.2.20020504191651.01c77c08@pop.freeserve.net>
On Sat, May 04, 2002 at 07:23:08PM +0100, Dave Pawson wrote:
> website, qandaentry processing is a simple apply-templates
> for all websites (I'm using chunk-website)
>
> The linking (local to page) down to page content is done
> via generate-id().
>
> I've had a request that these remain static as more
> entries are added.
> Although qandaentry has an id attribute in the DTD,
> when I use it, its ignored (overriden).
>
> Unsure where the actual toc is generated,
> website.xsl doesn't match the appearance,
>
> should I be overriding a template with customisation,
> or is this a more general feature that's programmed in
> to the main stylesheets please?
>
> Any advice appreciated.
The problem is the main stylesheets.
The short answer is to put your id attributes on the <question>
elements inside the <qandaentry> elements. The TOC
actually lists question elements, and will use that id
as a stable link name.
But I think when people create an xref to a qandaentry,
they don't target the id on the question element to do so.
So your feature request should be to change the TOC
generator to list qandaentry elements and use the question
element as the generated text only. And xrefs to
quandaentry should do the same (if they don't already).
--
Bob Stayton 400 Encinal Street
Publications Architect Santa Cruz, CA 95060
Technical Publications voice: (831) 427-7796
Caldera International, Inc. fax: (831) 429-1887
email: bobs@caldera.com