On 9/14/25 7:47 AM, Patrice Dumas wrote:
On Sun, Sep 14, 2025 at 07:20:57AM -0700, Raymond Toy wrote:
On 9/14/25 2:52 AM, Patrice Dumas wrote:
The default is:
pygmentize -f html -O noclasses=True
It is generic enough, I believe. My feeling is that it covers most use
cases, although using a wrapper script would also be ok.
However, Maxima's manual supports dark mode now and the default pygmentize
command above gets in the way of auto dark mode because I can't control the
colors via CSS.
So an external script where I can just write |pygmentize -f html| would work
quite well. I did hack up texinfo to remove the |-O noclasses=True|, and
could use CSS to select appropriate colors for both light and dark modes.
Right now, with the development sources, you could call texi2any like:
./texi2any.pl --html -c HIGHLIGHT_SYNTAX='pygmentize -f html -l ' maxima.texi
Sorry for the really long delay. I finally got around to testing this
out the latest git version of texinfo. It works just fine with a minor
tweak that it should be |pygmentize -f html -l %l|.
And AFAICT, there are no conflicts. I updated the CC for the maxima
manual to include CSS for the default style and a dark style. The
examples show up with the expected colors in both the light and dark style.
Thanks for adding support for this!
Side note: texinfo now complains about a zillion issues about node
pointers being messed up and also not in the appropriate menus. I guess
these are real issues in the manual that should be fixed. This happens
when building the info files. I don't see it when building the html or
pdf files.
to get the output you want (if I understood well).
Subject to change until an agreement is reached on the interface.
​
