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] indexterm with zone attribute


Bob,

Thanks for the explanation.  I'm not surprised that the stylesheets
don't support this feature (though I was hoping:-).

I'll go to the standard method for handling ranges.

Thanks,
Dick

> -----Original Message-----
> From: Bob Stayton [mailto:bobs@sagehill.net] 
> Sent: Sunday, June 29, 2008 4:43 PM
> To: Richard Hamilton; docbook-apps@lists.oasis-open.org
> Subject: Re: [docbook-apps] indexterm with zone attribute
> 
> 
> Hi Dick,
> The other suggestions made by Thomas and Dave are the 
> practical methods for 
> getting an indexterm zone to work with DocBook XSL.  TDG does 
> say that 
> putting a reference to a single xml:id in the zone attribute 
> should give you 
> a range that matches the size of that element.  But the 
> stylesheets have not 
> implemented that, because it is hard to do with XSL-FO.  It 
> would require 
> putting an empty anchor at the end of each element that has such a 
> reference, so that the second page reference can be generated 
> by the XSL-FO 
> processor.  There are lots of elements that can produce 
> ranges of pages, and 
> the templates for all those elements would have to perform 
> that function of 
> checking for such zone ranges.  That requires touching a lot 
> of templates.
> 
> Bob Stayton
> Sagehill Enterprises
> bobs@sagehill.net
> 
> 
> ----- Original Message ----- 
> From: "Richard Hamilton" <rlhamilton@frii.com>
> To: <docbook-apps@lists.oasis-open.org>
> Sent: Friday, June 27, 2008 2:25 PM
> Subject: [docbook-apps] indexterm with zone attribute
> 
> 
> > I've been indexing a document and am having some trouble 
> with the zone
> > attribute on indexterm.
> >
> > When the zone attribute points to an id on a block that extends over
> > more than one page, I would expect to see a range in the 
> output, but I
> > only see the first page.  Is that the expected output or is there a
> > problem somewhere?
> >
> > Here is a sample:
> >
> > <section xml:id="someid"><title>some title</title>
> > ... section contents long enough to extend over
> >    more than one page...
> > </section>
> >
> > If I use this indexterm (placed inside the section, though 
> I'm not sure
> > that's relevant):
> >
> > <indexterm zone="someid"><primary>topic</primary></indexterm>
> >
> > and this section extends from page 4 to 6, I would expect the index
> > entry to look like this:
> >
> > topic, 4-6
> >
> > However, instead of the range 4-6, I'm just getting the start of the
> > range, like this: topic, 4
> >
> > Does anyone know if I should be getting a range, and if so, is there
> > some parameter or other magic that I need to use to get a 
> range?  I'm
> > familiar with the other style of getting ranges in indexes, 
> but since
> > I've already got ids on the appropriate sections, I'd 
> rather use this
> > method if I can get it to work.
> >
> > I'm using DB 5.0, stylesheets 1.74.0, Saxon 6.5.3, fop 0.94, and the
> > basic index algorithm (though the same thing happens with the Kosek
> > index algorithm).
> >
> > Thanks,
> > Dick Hamilton
> > http://rlhamilton.net
> >
> >
> >
> >
> >
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: 
> docbook-apps-unsubscribe@lists.oasis-open.org
> > For additional commands, e-mail: 
> docbook-apps-help@lists.oasis-open.org
> >
> >
> > 
> 
> 




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