bug-texinfo
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: @subentry, @seealso and @seenentry better formatted in HTML


From: Per Bothner
Subject: Re: @subentry, @seealso and @seenentry better formatted in HTML
Date: Sat, 19 Nov 2022 04:09:05 -0800
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.1



On 11/19/22 01:22, Patrice Dumas wrote:
@findex f---bb @subentry f---cc

the HTML is:

<tr><td></td><td class="printindex-index-entry"><code>f---bb</code></td><td>&nbsp;</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>&nbsp;</td><td class="printindex-index-section"><a href="#chapter">1 
chapter</a></td>

We really shouldn't be using '&nbsp;' or empty table cells for formatting.
Use CSS. For example:

<style>
  span.index-entry-level-1 {padding-left: 2em }
  td.printindex-index-section { padding-left: 1em }
</style>

Better of course if we we could nest the subentries within the super entries,
and maybe avoid using tables altogether. It miight be possible using grids
(and maybe subgrids), but they're relatively new, and I haven't used them.

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?

That would be fairly easy to deal with.
However, JavaScript should be able figure it out without that.
It can look at sibling entries wihout too much pain,
as long as there is a clean well-defined structure:
It is easy to tell entries, subentries, and subsubentries apart,
and they're in the "obvious" order.
--
        --Per Bothner
per@bothner.com   http://per.bothner.com/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]