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

2022-11-20 Thread Per Bothner
On 11/20/22 13:47, Patrice Dumas wrote: On Sun, Nov 20, 2022 at 01:35:33PM -0800, Per Bothner wrote: Before I do that, I suggest cleaning up the generated html a bit, as discussed: - Get rid of the dummy table cells used for indentation. The first column is the letter column. It is not re

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

2022-11-20 Thread Patrice Dumas
On Sun, Nov 20, 2022 at 01:35:33PM -0800, Per Bothner wrote: > Before I do that, I suggest cleaning up the generated html a bit, as > discussed: > - Get rid of the dummy table cells used for indentation. The first column is the letter column. It is not really indentation, although it indeeds le

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

2022-11-20 Thread Per Bothner
Looking at the latest checkins, I suggest replacing: /* Scan links that should be added to the index. */ var index_links = document.querySelectorAll ("td.printindex-index-entry a"); by: /* Scan links that should be added to the index. */ var

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

2022-11-20 Thread Patrice Dumas
On Sun, Nov 20, 2022 at 11:33:53AM -0800, Raymond Toy wrote: > On Sun, Nov 20, 2022 at 11:24 AM Patrice Dumas wrote: > > On small screens a level two subentry would lead to too much > > indentation. But using 2 and 4 would already indent much more. I'll > > see if it looks ok. > > > > Ah, yes,

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

2022-11-20 Thread Raymond Toy
On Sun, Nov 20, 2022 at 11:24 AM Patrice Dumas wrote: > On Sun, Nov 20, 2022 at 11:07:34AM -0800, Raymond Toy wrote: > > > > 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 eno

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

2022-11-20 Thread Patrice Dumas
On Sun, Nov 20, 2022 at 11:07:34AM -0800, Raymond Toy wrote: > > 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

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

2022-11-20 Thread Raymond Toy
On Sat, Nov 19, 2022 at 1:22 AM Patrice Dumas 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=76485d9ea1f8e411b6b4e419

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

2022-11-20 Thread Patrice Dumas
On Sun, Nov 20, 2022 at 10:49:06AM +, 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 a

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

2022-11-20 Thread Gavin Smith
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

Re: set INDEX_ENTRY_COLON to ''?

2022-11-20 Thread Gavin Smith
On Sat, Nov 19, 2022 at 06:01:14PM +0100, Patrice Dumas wrote: > Hello, > > I find the colon produced between index entries and nodes/sections in > printindex HTML formatting to be quite ugly, and uneeded, as the table > is already providing the structure. Is it only me? > > What about setting i