[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [docbook-apps] db5, index processing
On Wed, 9 Feb 2011 10:24:45 -0800 "Bob Stayton" <bobs@sagehill.net> wrote: > Hi Dave, > Currently the itermset element is not processed by the stylesheet. > The reason you see an entry in the index is because the template that > builds the index uses select="//indexterm" to locate all indexterms > in the document, regardless of their location inside any element. > The problem is that because itermset is not processed, there is no > anchor placed in the output for its indexterms. You get an index > entry, but there is no where for it to go, because there is no anchor > placed in the FO or HTML output. So you get an index entry with no > page number. > > This seems to be an unfinished part of the stylesheets. Could you > please file a bug report on the SourceForge bug tracker to add > support for itermset. > > I think info/itermset/indexterm elements without a zone attribute are > a bit ambiguous. The metadata for an element does not have a specific > location in the output (a page in PDF output). Usually metadata is > presented at the start of the element, but that is a convention that > is not defined for itermset. TDG says indexterm elements in itermset > should have a zone attribute to identify which content (and pages) it > applies to. > > Bob Stayton > Sagehill Enterprises > bobs@sagehill.net Bug 3179611 submitted. DaveP > > > ----- Original Message ----- > From: "Dave Pawson" <davep@dpawson.co.uk> > To: <docbook-apps@lists.oasis-open.org> > Sent: Monday, February 07, 2011 1:31 AM > Subject: [docbook-apps] db5, index processing > > > > > > running a book through db5 to xsl-fo. > > > > Input has info/itermset to hold a couple of index terms. > > > > xep shouts that > > [error] no entries for index key 'xxxx' where xxx is content of the > > primary child of indexterm. > > > > The entry is there in the output PDF, but I find it odd that xep is > > complaining? > > > > Is it just that there is no text in the fo to which it should > > (normally) refer? > > > > Just wanted to confirm the processing is as expected. > > > > > > > > > > -- > > > > regards > > > > -- > > Dave Pawson > > XSLT XSL-FO FAQ. > > http://www.dpawson.co.uk > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > > docbook-apps-unsubscribe@lists.oasis-open.org For additional > > commands, e-mail: docbook-apps-help@lists.oasis-open.org > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org > For additional commands, e-mail: > docbook-apps-help@lists.oasis-open.org > -- regards -- Dave Pawson XSLT XSL-FO FAQ. http://www.dpawson.co.uk
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]