This is the mail archive of the
docbook-apps@lists.oasis-open.org
mailing list .
Re: Treatment of links in print
- From: Bob Stayton <bobs at caldera dot com>
- To: kdunn at hsc dot edu, docbook-apps at lists dot oasis-open dot org
- Date: Wed, 05 Jun 2002 16:01:32 -0700
- Subject: Re: DOCBOOK-APPS: Treatment of links in print
- References: <200206051849.AA589758642@hams-hsc.hsc.edu>
On Wed, Jun 05, 2002 at 06:49:23PM -0400, Kevin Dunn wrote:
>
>
> >to give
> >I would like to render
> ><para>
> >For an example of this procedure, refer to
> ><link linkend="foo">Foo</link>
> ></para>
> >
> >As
> >
> >"For an example of this procedure, refer to Foo (p. 29)"
> >
> >Where 29 is the page. I'd also be satisfied with
> >
> >"1.2.3 Foo" where 1.2.3 is the subsection.
> >
>
> You could use, for example
> <section id="foosection">
> ...
> <para id="foopara">This is the part that talks about foo.</para>
> ...
> </section>
> ...
> <para>
> For an example of this procedure, refer to
> <link linkend="foopara">Foo</link>(<xref linkend="foosection">).
> </para>
>
> Unlike link, xref generates its own text, depending on its target.
> This markup should produce something like:
>
> For an example of this procedure, refer to Foo (Section 1.2.7).
>
> I don't know how to do page numbers. Gotta be possible, since the TOC
> does it.
If this is being processed with the XSL stylesheets,
try setting the stylesheet parameter
'insert.xref.page.number' to 1 in a customization
layer. It's supposed to do that, but I've not
tried it with the current versions of the FO processors.
--
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