On Sat, Nov 19, 2022 at 1:22 AM Patrice Dumas <pertu...@free.fr> wrote:
> Hello, > > Some formatting for @subentry, @seenentry and @seealso in HTML more in > line with TeX output has been implemented in the developpement source: > > > https://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=76485d9ea1f8e411b6b4e4196babe1089d286a42 > > https://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=cf772b028c696fc58b42d17363e0334af5e5c7d4 > > (Discussed in > ttps://lists.gnu.org/archive/html/bug-texinfo/2022-08/msg00103.html). > Thank you so much for working on this! It looks way better and more useful than the old way. The only issue I have is that the subentries aren't indented enough. I think it would be easier to read if they were indented by default by, say, about 4 chars or so to make the subentries stand out a bit more. If you glance at the index, it's easy to miss that the items are indented. I haven't tried anything with @seentry or @seealso. > > For @seenentry and @seealso, I am not sure about the classes to use, but > my impression is that the formatting is ok. > > for @subentry, I am less sure, as the implementation uses different > table lines and indentation with a <span>. In addition, the change has > probably implications on the info.js reader. A @subentry is rendered as > different lines in table, only the last one having a <a> to link to the > index entry and to the section or node containing the index entry. For > example, for > > @findex f---bb @subentry f---cc > > the HTML is: > > <tr><td></td><td > class="printindex-index-entry"><code>f---bb</code></td><td> </td><td > class="printindex-index-section"></td></tr> > <tr><td></td><td class="printindex-index-entry"><span > class="index-entry-level-1"><a > href="#index-f_002d_002d_002dbb"><code>f---cc</code></a></span></td><td> </td><td > class="printindex-index-section"><a href="#chapter">1 chapter</a></td> > > In this case there is only one entry with f---bb as amin entry, but if > there was another one, it could be before the part corresponding to > @subentry f---cc. > > Any proposition for a better formatting? Any idea on how to help > javascript-ing, maybe with a custom attribute with the full entry with > commas separating the subentries? > > -- > Pat > > -- Ray
