Re: Relating multiple index entries to one table item

2022-11-26 Thread Eli Zaretskii
> From: Arsen Arsenović > Cc: Patrice Dumas , Eli Zaretskii , > help-texinfo@gnu.org > Date: Sat, 26 Nov 2022 21:40:53 +0100 > > I was still interested in indexing @itemx', so I tried: > > @table @code > @vindex ABC > @item ABC > @vindex DEF > @itemx DEF IME, such usage makes little

Re: Relating multiple index entries to one table item

2022-11-26 Thread Patrice Dumas
On Sat, Nov 26, 2022 at 11:11:52PM +0100, Patrice Dumas wrote: > It is a help for formats that have restrictions on what can be in > tables. Maybe would be a good think to check that the DocBook is also > valid. Seems like that it is better as index entries are better in in DocBook too. --

Re: Relating multiple index entries to one table item

2022-11-26 Thread Patrice Dumas
On Sat, Nov 26, 2022 at 08:18:43PM +, Gavin Smith wrote: > On Sat, Nov 26, 2022 at 03:59:00PM +, Gavin Smith wrote: > > I still haven't put index entries before the very first > > @item in a @table inside the - I need to do something with the > > 'before_item' element. > > It should be

Re: Relating multiple index entries to one table item

2022-11-26 Thread Arsen Arsenović
Gavin Smith writes: > On Sat, Nov 26, 2022 at 03:59:00PM +, Gavin Smith wrote: >> I still haven't put index entries before the very first >> @item in a @table inside the - I need to do something with the >> 'before_item' element. > > It should be done now. I tried never adding a

Re: Relating multiple index entries to one table item

2022-11-26 Thread Gavin Smith
On Sat, Nov 26, 2022 at 03:59:00PM +, Gavin Smith wrote: > I still haven't put index entries before the very first > @item in a @table inside the - I need to do something with the > 'before_item' element. It should be done now. I tried never adding a 'before_item' element in the first

Re: Relating multiple index entries to one table item

2022-11-26 Thread Arsen Arsenović
Patrice Dumas writes: > This should be fixed by > https://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=3ae7857e9f958386864f5ad4b7536ae50a130c8b Ah, thanks. I already tried to send this patch in, but apparently that failed and I never noticed. Can confirm it does fix the issue. -- Arsen

Re: Relating multiple index entries to one table item

2022-11-26 Thread Patrice Dumas
On Sat, Nov 26, 2022 at 05:49:54PM +0100, Arsen Arsenović wrote: > > I wanted to give implementing that an attempt, but while trying to > configure and build the texinfo trunk, I get: This should be fixed by

Re: Relating multiple index entries to one table item

2022-11-26 Thread Patrice Dumas
On Sat, Nov 26, 2022 at 05:49:54PM +0100, Arsen Arsenović wrote: > > Gavin Smith writes: > > > I have nuked the relate_index_entries_to_table_entries transformation > > which made this association. According to the changelog, I introduced > > this code in November 2020. This may remove some

Re: Relating multiple index entries to one table item

2022-11-26 Thread Arsen Arsenović
Gavin Smith writes: > I have nuked the relate_index_entries_to_table_entries transformation > which made this association. According to the changelog, I introduced > this code in November 2020. This may remove some copiable anchors from > HTML manuals, for @item in @table. We'll have to

Re: Relating multiple index entries to one table item

2022-11-26 Thread Patrice Dumas
On Sat, Nov 26, 2022 at 04:45:24PM +, Gavin Smith wrote: > On Wed, Nov 23, 2022 at 11:56:30PM +0100, Patrice Dumas wrote: > > As I said before I do not think that it is right to merge the first > > index entry with the @item, but that's a separate issue. > > I have nuked the

Re: Relating multiple index entries to one table item

2022-11-26 Thread Gavin Smith
On Sat, Nov 26, 2022 at 05:19:17PM +0100, Patrice Dumas wrote: > I just pushed a commit which removes _open_table_term_type. Feel free > to revert it if you need to. LGTM, thanks.

Re: Relating multiple index entries to one table item

2022-11-26 Thread Gavin Smith
On Wed, Nov 23, 2022 at 11:56:30PM +0100, Patrice Dumas wrote: > As I said before I do not think that it is right to merge the first > index entry with the @item, but that's a separate issue. I have nuked the relate_index_entries_to_table_entries transformation which made this association.

Re: Relating multiple index entries to one table item

2022-11-26 Thread Patrice Dumas
On Sat, Nov 26, 2022 at 03:58:59PM +, Gavin Smith wrote: > On Thu, Nov 24, 2022 at 12:07:47AM +0100, Patrice Dumas wrote: > > It is also possible to do something when the element is first > > encountered, with $default_types_open{'table_term'} = > > \&_open_table_term_type; > > though I am

Re: Relating multiple index entries to one table item

2022-11-26 Thread Patrice Dumas
On Sat, Nov 26, 2022 at 03:58:59PM +, Gavin Smith wrote: > On Thu, Nov 24, 2022 at 12:07:47AM +0100, Patrice Dumas wrote: > > It is also possible to do something when the element is first > > encountered, with $default_types_open{'table_term'} = > > \&_open_table_term_type; > > though I am

Re: Relating multiple index entries to one table item

2022-11-26 Thread Gavin Smith
On Thu, Nov 24, 2022 at 12:07:47AM +0100, Patrice Dumas wrote: > It is also possible to do something when the element is first > encountered, with $default_types_open{'table_term'} = \&_open_table_term_type; > though I am not sure at all that it would help you. I used this, thanks. I opened at

Re: Relating multiple index entries to one table item

2022-11-26 Thread Gavin Smith
On Sat, Nov 26, 2022 at 03:04:37PM +0100, Patrice Dumas wrote: > I thought a bit more on that issue, and indeed, even if the index > entries lead to the @item when they are before the item, it could still > make sense to reparent them to the @item, at the beginning instead of > being before the

Re: Relating multiple index entries to one table item

2022-11-26 Thread Patrice Dumas
On Fri, Nov 25, 2022 at 10:12:21PM +, Gavin Smith wrote: > On Tue, Nov 22, 2022 at 09:49:33PM +, 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