Re: Relating multiple index entries to one table item

On Tue, Nov 22, 2022 at 09:49:33PM +0000, Gavin Smith wrote:
> On Tue, Nov 22, 2022 at 10:23:24PM +0100, Patrice Dumas wrote:
> > Maybe not important if there are other changes afterwards, but with the
> > change, in HTML, the result is now invalid, as the index entries end up
> > not associated with the index term <dt>, but after the index term.  This
> > is not correct, as the outer <dl> should only contain <dl> and <dt>.  It
> > may not be an issue at all if you do further changes, or it could be an
> > issue to be solved in the HTML converter.
> 
> I'll check this output and see I can change it to be valid again.

I've reverted my change as I couldn't make it work out right and it is
not clearly right.

I'm starting to think that it should be index entries *before* the @item that
are associated with the @item, not after it.  I feel this may be easier to
implement.  This would leave the Info output unaltered.

There may be a related issue with associating index entries with other
constructs.  For example, a paragraph:

    @cindex paragraph 1
    This is a paragraph.

outputing in HTML as

    <a class="index-entry-id" id="index-paragraph-1"></a>
    <p>This is a paragraph.
    </p>

Arguably, the following may be better:

    <p id="index-paragraph-1">This is a paragraph.
    </p>

However, this may be more difficult to achieve than just focusing on
the @table case.