From: W. Eliot Kimber (email@example.com)
Date: Thu Mar 27 2003 - 08:00:35 PST
David Tolpin wrote:
>>This is a limitation of the XEP indexing extensions--you have no control
>>over which sequences of page numbers will result in ranges.
> You do.
> If rx:key is specified on a markup element that spans more than one page, than
> that will result in a range. If it is specified on two elements on two subsequent
> pages, than there will be to separate page numbers.
Hmm--I'm not sure this solves the problem though, because it may not be
possible or practical to construct a containing flow object that exactly
demarcates the start and end of my desired range.
That is, if I have the sort of "<start-range/> ... <end-range/>" markup
that one would normally use to specify index ranges in the source, I
can't think of a way to reliably translate that to a block that exactly
contains the range--it likely crosses the normal flow object hierarchy
produced by the non-index input elements.
By the same token, just pushing the rx:key to the parent page-spanning
block wouldn't always be appropriate because that block might extend
farther than the intended range. This would be the case, for example,
when the index range reflects a sequence of paragraphs in a larger
container, where the sequence of paragraphs is not otherwise identified
by containment. In this particular case I might be able to synthesize a
block that contains just those paragraphs, but doing so would seriously
complicate the XSLT process (because I'd have to check for index ranges
at the start of every paragraph and then verify that the range didn't
cross a structural boundary that would result in a structural boundary
in the result FO). I guess if you structured your FO so there was little
or no containment around the leaf blocks, it would be a little easier,
but then you wouldn't get the benefit of property propogation.
-- W. Eliot Kimber, firstname.lastname@example.org Consultant, ISOGEN International 1016 La Posada Dr., Suite 240 Austin, TX 78752 Phone: 512.656.4139 ------------------- (*) To unsubscribe, send a message with words 'unsubscribe xep-support' in the body of the message to email@example.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
This archive was generated by hypermail 2.1.5 : Thu Mar 27 2003 - 07:53:43 PST