[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: @subentry, @seealso and @seenentry better formatted in HTML
From: |
Gavin Smith |
Subject: |
Re: @subentry, @seealso and @seenentry better formatted in HTML |
Date: |
Sun, 20 Nov 2022 10:49:06 +0000 |
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.
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.
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
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.
- @subentry, @seealso and @seenentry better formatted in HTML, Patrice Dumas, 2022/11/19
- Re: @subentry, @seealso and @seenentry better formatted in HTML, Per Bothner, 2022/11/19
- Re: @subentry, @seealso and @seenentry better formatted in HTML, Patrice Dumas, 2022/11/19
- Re: @subentry, @seealso and @seenentry better formatted in HTML, Per Bothner, 2022/11/19
- Re: @subentry, @seealso and @seenentry better formatted in HTML, Patrice Dumas, 2022/11/19
- Re: @subentry, @seealso and @seenentry better formatted in HTML,
Gavin Smith <=
- Re: @subentry, @seealso and @seenentry better formatted in HTML, Patrice Dumas, 2022/11/20
Re: @subentry, @seealso and @seenentry better formatted in HTML, Patrice Dumas, 2022/11/19
Re: @subentry, @seealso and @seenentry better formatted in HTML, Raymond Toy, 2022/11/20
Re: @subentry, @seealso and @seenentry better formatted in HTML, Per Bothner, 2022/11/20