Re: [Scrollkeeper-devel] extracted index

[Mary D. <Mar...@Su...>]

Laszlo Kovacs wrote:
> > 
> > 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. 

- yes, it's because there are two indexterm entries in the original document as 
follows:
<indexterm id="idx-a2"><primary>Panel</primary></indexterm>
<indexterm id="idx-a9"><primary>Panel</primary></indexterm>

granted, in a correctly written help document this shouldn't occur ...

> 
> 
> > 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.

- ok, can name it 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?

- it's due to the way I'm generating the ids. In the above example when the 
stylesheet is outputing the Main Menu, Example entry it generates an id and 
outputs it (id10791). Then when the <see> entry (Chapter, Example) is being 
output, need to be able to match the <see> content to the correct indexterm. 
This is done by means of keys, so need to know how the <see>content is written 
in order to construct the keys. ...... If this restriction is an issue I can do 
some more investigation - may be able to solve it using the translate function 
to eliminate commas, spaces for the key ....


Mary
 
> 
> Laszlo

~ I speak for myself, not for my employer ~
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Mary Dwyer
Desktop Applications & Middleware Grp
Sun Microsystems Ireland
Tel: +353-1-8199222 (xt 19222)
Fax: +353-1-8199078
email: mar...@ir...
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=