>>>>> "Peter" == Peter Toft <pto@sslug.dk> writes:

Peter> On 21 Apr 2001, Edward C. Bailey wrote:
...
>>  I've done a bit with it (I hacked up a new frontend and backend for jw
>> that uses collateindex.pl and did some cursory testing under the 7.1
>> beta).  I've done tried it on the gold bits yet; after I give it a try,
>> I'll post it here if you like...

Peter> It sure would be nice to know how to get RH 7.1 docbook tools to
Peter> work - so please do :) Using collateindex.pl seems to be
Peter> non-trivial.

It's not that bad, really.  Basically you run your SGML through jade once
to get an HTML index file; then you run collateindex.pl against this,
creating a DocBook index.  Finally, you run your SGML (including the
newly-generated index) through jade one last time.

Some notes on these scripts:

    o Minimal testing, blah, blah, blah, it's somewhat stupid, blah, blah,
      blah, works for me, blah, blah, blah... :-)

    o Usage is:

<path-to-script>/flo-db2indexed-html <SGML-file>.sgml

    o Puts final output in a subdirectory called <SGML-file>

    o Assumes the following entity definition and reference is in the SGML
      file:

<!ENTITY GENERATED-INDEX SYSTEM "generated-index.sgml">

      And where ever you want the index to appear:

&GENERATED-INDEX;

      (The script will recreate generated-index.sgml each time it runs; the
      first time jade runs there will be no file by this name, so you'll
      see an error.)

    o Assumes that any graphics referenced in the SGML reside in a
      subdirectory called "figs".  This subdirectory is copied into the
      <SGML-file> subdirectory, so the entire <SGML-file> directory tree
      can be tarred up, and dropped on a website, ready to go...

    o flo-db2indexed-html refers to a .dsl file that we've hacked, but this
      should be removable so the default DSSSL is used instead.

I think that's about it...

                                Enjoy,

                                    Ed