[xep-support] creating index with XEP extensions

[Bob Stayton]

Each <indexterm> has to output an fo element with an id attribute at the
location where the indexterm occurs in the document.   The id is the target
of the index reference.  It is likely that there are situations in your
stylesheet where the indexterm is not outputting its anchor for some reason.
Perhaps indexterm in certain element templates is not reached, or a template
handles certain children but not others.  You are getting an entry in the
index itself because the stylesheet is probably using a global path to
collect them, such as //indexterm.

This problem just came up on the docbook-apps mailing list because an
indexterm in a sectioninfo element was not outputting its id element.

Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs at sagehill.net


----- Original Message ----- 
From: "CRW150 at yahoo.com" <crw150 at yahoo.com>
To: <xep-support at renderx.com>
Sent: Friday, April 08, 2005 9:20 AM
Subject: [xep-support] creating index with XEP extensions


> Hi,
>
> When I create an index using the XEP "index.xsl" stylesheet, I get an
> error message on *some* <indexterm> entries. The error message is:
>
> [error] no entries for index key 'foo'
> [error] no entries for index key 'foo-primary'
>
> I know those entries are in the source document, and they are properly
> tagged. And otherwise, my index looks fine with all the proper entries
> and links.
>
> How can I go about finding out why these few indexterms are being
> missed or ignored?
>
> I am doing a transformation to .pdf. Does XEP first create an
> 'intermediate' .fo file to pass to the final transformation? Is there a
> way to look at that file?
>
> BTW, documentation says that the default for
> "merge-subsequent-page-numbers" is 'false'. How do I set it to 'true'?
> I'm no programmer, so please be specific--like, I need the exact
> syntax. :)
>
> Thanks,
> Susan
> (If it matters, I'm running WinXP and my XEP is version 4.0.)
>
>
>
> __________________________________
> Yahoo! Messenger
> Show us what our next emoticon should look like. Join the fun.
> http://www.advision.webevents.yahoo.com/emoticontest
> -------------------
> (*) To unsubscribe, send a message with words 'unsubscribe xep-support'
> in the body of the message to majordomo at renderx.com from the address
> you are subscribed from.
> (*) By using the Service, you expressly agree to these Terms of Service
http://www.renderx.com/tos.html
>
>


-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to majordomo at renderx.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/tos.html