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

[Patrice Dumas]

On Sun, Nov 20, 2022 at 10:49:06AM +0000, Gavin Smith wrote:
> On Sat, Nov 19, 2022 at 08:35:34PM +0100, Patrice Dumas wrote:
> > I think that it is less practical than padding-left, I will use
> > padding-left as you initially suggested.
> 
> We have to be careful about relying on CSS.

I try to always think about what could be the output without CSS when
there is some change.

> For information, I checked the new index output in the "links" webbrowser
> (which is a text terminal browser and doesn't use CSS) and the output
> appeared fine - there was always at least one space between the two columns.

Another way to look at the result without CSS is to review in a
webbrowser the file obtained with html32.pm, that's what I do in general
rather than looking at the result in a browser without CSS.  The file
is:
tp/tests/layout/res_parser/formatting_html32/formatting.html

> This was also the case with "w3m".
> 
> The tables in "lynx" are not lined up at all but this is a known limitation
> of this program.
> 
> I think in a graphical webbrowser without CSS, the worst that
> can happen here is that for the occasional index entry, there is

For the longest index entry, actually.

> little or no space between it and the node link in the next column.
> This seems like a price worth paying to get rid of all the  
> from the output, so I am happy with this change.

Disadvantages of the   column were that it could not be customized at
all in CSS, and also that an extra column looked bad if it becomes
visible, for example if table lines were colored.

-- 
Pat