On Sat, Nov 19, 2022 at 04:09:05AM -0800, Per Bothner wrote:
>
> On 11/19/22 01:22, Patrice Dumas wrote:
> > 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
On Sat, Nov 19, 2022 at 09:30:30AM -0800, Per Bothner wrote:
>
>
> On 11/19/22 08:58, Patrice Dumas wrote:
> > I have modified span.index-entry-level-1 to use padding-left instead of
> > margin-left, but to have some space between the td elements, shouldn't
> > margin-left be preferable?
>
> Pad
On 11/19/22 08:58, Patrice Dumas wrote:
I have modified span.index-entry-level-1 to use padding-left instead of
margin-left, but to have some space between the td elements, shouldn't
margin-left be preferable?
Padding adds extra space "within" an element, while margin adds extra space
betwe
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 it to '' in the default case?
(It is alreadu '' in the texi2html style).
--
On Sat, Nov 19, 2022 at 04:09:05AM -0800, Per Bothner wrote:
>
>
> We really shouldn't be using ' ' or empty table cells for formatting.
> Use CSS. For example:
>
>
> span.index-entry-level-1 {padding-left: 2em }
> td.printindex-index-section { padding-left: 1em }
>
I have modified span.i
On 11/19/22 01:22, Patrice Dumas wrote:
@findex f---bb @subentry f---cc
the HTML is:
f---bb
f---cc 1
chapter
We really shouldn't be using ' ' or empty table cells for formatting.
Use CSS. For example:
span.index-entry-level-1 {padding-left: 2em }
td.printindex-index-section { paddi
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/comm
On Fri, Nov 18, 2022 at 05:40:51PM -0800, Per Bothner wrote:
> On 11/18/22 14:43, Gavin Smith wrote:
> > Unfortunately, it has various obvious problems. Most significantly, the
> > index search does not work.
>
> The problem is line 1459 in info.js:
>
> var index_links = document.queryS
