On Sat, Jul 26, 2025 at 11:13:35PM +0100, Gavin Smith wrote: > On Sat, Jul 26, 2025 at 11:45:53PM +0200, Patrice Dumas wrote: > > On Sat, Jul 26, 2025 at 10:07:03PM +0100, Gavin Smith wrote: > > > A simple solution would be to avoid outputting the > > > "printindex-index-entry" > > > class for index subentries and to put all the needed rules on both > > > classes. > > > > It looks good to me. It could also be possible to take that opportunity > > to add some subentry somewhere in the index-entry-level-1 if it is only > > for subentries, like > > index-subentry-level-1 > > I realised that any change to these CSS classes would likely have a knock-on > effect for the info.js JavaScript browsing enhancement (with the INFO_JS_DIR > variable for texi2any). It's probably manageable to update, though. > > Should we add the name of the command, so current > > <td class="printindex-index-entry index-entry-level-1"> > > would become the following? > > <td class="printindex-index-subentry-level-1">
That would be ok, as we are in printindex. The subentry should not be first as, even if we are formatting a subentry, we are not at the location of the subentry in the tree. -- Pat
