Re: [Scrollkeeper-devel] extracted index

[<las...@Su...>]

Mary Dwyer wrote:
> 
> hi
> 
> attached is an example of an index extracted using the stylesheet I've written
> for scrollkeeper.  I'd appreciate if you could have a look at it and provide
> some feedback.
> 
> A few issues to note:
> 1. only dealing with indexterms from the original document that include an "id"
> or "zone" attribute (in order to provide anchors back to the original document)
> 
> 2. If an indexterm occurs more than once in the original document then will
> result in a duplicate entry such as this eg.
>  <primary>
>     <title linkid="idx-a2" id="id10715">Panel</title>
>     <title linkid="idx-a9" id="id10715">Panel</title>
> 
>     - this is not ideal, but not sure how to get round this.
We probably need to find some solution for this. Is this like there are
actually two different Panel descriptions in the text? Because if yes
then the document is probably incorrectly written. 


> 3.  ids are generated within the index to provide internal links for see and
>     seealso references. For example, where "Main Menu, Example" is an index
> entry, and there is a see reference from "Chapter, Example" to "Main Menu,
> Example" the output will be as follows:
> 
> <primary>
>     <title>Chapter</title>
>     <secondary>
>       <title>Example</title>
>       <see id="id10791">Main Menu, Example</see>
>     </secondary>
>   </primary>
>   <primary>
>     <title>Main Menu</title>
>     <secondary>
>       <title linkid="idx-a3" id="id10791">Example</title>
>     </secondary>
>   </primary>

Isnt there a restriction that id attributes have to be unique throughout
the document? If it is then we will need to name the "id" attribute
something else.
 
>  In order to be able to match the <see>/<seealso> content to the correct index
> term I need to be able to assume the <see>/<seealso> content will be structured
> in a set way, ie primary, secondary, tertiary (each term seperated by a comma
> and a space - or whatever, once it is consistent).
This might be a problem considering the variety of sources documents are
coming from. Why is this needed?

Laszlo