OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [docbook-apps] Font familiy of some automatically generated index-entries

----- Original Message ----- 
From: "Joachim Ziegler" <ziegler@mpi-sb.mpg.de>
To: "Bob Stayton" <bobs@sagehill.net>
Cc: "docbook-apps" <docbook-apps@lists.oasis-open.org>
Sent: Tuesday, February 10, 2004 2:30 AM
Subject: Re: [docbook-apps] Font familiy of some automatically generated

> Bob Stayton wrote:
> >
> > But actually, you can accomplish this without customizing the
> > stylesheet at all.  You can do it entirely in your source document.
> > The sortas attribute can be used to separate them:
> >
> > <indexterm><primary>stack</primary></indexterm>
> > <indexterm><primary sortas="stack classname">
> >      <classname>stack</classname></primary></indexterm>
> >
> > If all the instances of the classname indexterm have a sortas attribute
> > that differs from the non-classname indexterms, then they will be
> > as different index entries.  You'll have to be careful to get them to
> > together if you have other "stack somethings".  You'll have to come
> > up with a naming scheme, maybe using a character that occurs
> > before all letters in the sort order.
> I've tried this with the three instances of the indexterm for "node" in
> my document:
> <indexterm><primary sortas="node general">node</primary></indexterm>
> ...
> <indexterm><primary sortas="node general">node</primary></indexterm>
> ...
> <indexterm><primary sortas="node
> typename"><type>node</type></primary></indexterm>
> Now, as you said, I got 2 different index entries, one for nodes (of a
> graph) in general rendered in proportional font, one for the C++ type
> node in fixed font.
> But unfortunately, the page numbers are repeated twice:
> node, 192, 261, 267
> node, 192, 261, 267
> Instead, the output should be:
> node, 192, 261
> node, 267

Very interesting.  When I look in the FO output, I see no duplicate
page references.  When I then process the FO with XEP, I see the
duplicate references.  When I use FOP or Antenna House, the page numbers are
correct.  So you must be using XEP.

When xep.extensions is set to 1, some extra elements are output to the
FO in the rx: namespace for the XEP processor to handle. Those extra
elements permit XEP to generate page ranges.  But the stylesheet
isn't using the sortas attribute in those extensions.  I'm filing a bug
to get this fixed.

Bob Stayton
Sagehill Enterprises
DocBook Consulting

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]