RE: [docbook-apps] Generating index.xml for an eclipse help plugin

["David Cramer" <dcramer@motive.com>]

Glad to hear it. 

I just tried a few experiments to see if the approach javahelp takes
would work in eclipse. The answer is not really. If you do this (i.e.
having an entry with no targets):

  <entry keyword="foo (see blah)"/>

Then that entry simply doesn't appear in the index. If you try this:

  <entry keyword="foo (see blah)">
	<topic/>
  </entry>

Or 

  <entry keyword="foo (see blah)">
	<topic href="#"/>
  </entry>

Then the index doesn't render at all.

This works, but you're left with a dead link in the index (assuming
there's no page named noop):

  <entry keyword="foo (see blah)">
	<topic href="noop"/>
  </entry>

So you _have_ to have a target for every index entry. So I'm not sure
what the right thing to do to support <see> and <seealso> is.

David

> -----Original Message-----
> From: Peter Desjardins [mailto:pdesjardins@supplyscape.com] 
> Sent: Thursday, October 11, 2007 1:32 PM
> To: David Cramer; Mauritz Jeanson; docbook-apps@lists.oasis-open.org
> Subject: RE: [docbook-apps] Generating index.xml for an 
> eclipse help plugin
> 
> > I committed a version of eclipse.xsl that does this (just a 
> matter of 
> > modifying some templates from javahelp.xsl). It works, but doesn't 
> > support see or seealso yet:
> > http://cia.vc/stats/project/docbook/.message/13b3ae
> > 
> > David
> 
> Thanks!  Your code works wonderfully in my customization layer.
> 
> I do use a few "see" entries and the behavior I am seeing is 
> that are rendered as normal index entries.  That could be worse.
> 
> I did not see any indication of how the Eclipse Infocenter 
> expects "see"
> and "seealso" entries represented in index.xml.  Perhaps it's 
> Eclipse that doesn't yet support them.
> 
> Peter Desjardins
>