|
From: Raymond T. <toy...@gm...> - 2023-05-26 00:16:32
|
On 5/25/23 09:06, Marco Lo Monaco wrote: > Thanks Robert, I guess there is no way to have the texi2html.init > already built. I noticed though that if I omit it in the command line If you're using texinfo 7.0 and later, you can just delete the @NEED_MATHJAX@ from texi2html-7.init.in. Texinfo 7 already specifies some version of mathjax automatically. And IIRC, the part about the polyfill was only needed for some older browsers, I think. The only reason we have texi2html-7.init and friends is to have the maxima html files numbered like maxima_1.html, maxima_2.html and so on. If you're doing your own texi file that's not part of maxima, you don't really need the texi2html.init file at all as long as you don't mind the names texinfo uses when splitting the document into multiple files. Unless your doc is huge, outputting a single html page is probably good enough. > I get the same results, so maybe it is only needed for connecting the > single package doc to the rest of the maxima manual. > Since my purpose is to create html doc for single packages (not to be > included in the whole maxima manual) I ended up using this command > line (thanks to to the tips from Raymond about Mathjax): > > texi2any --html -c OUTPUT_ENCODING_NAME=UTF-8 > --css-include=./manual.css --init-file ./texi2html.init.in --no-split > template-standalone.texi --set-customization-variable > HTML_MATH=mathjax --set-customization-variable EXTRA_HEAD='<link > rel="icon" href="figures/favicon.ico"><script > src="https://polyfill.io/v3/polyfill.min.js?features=es6>"></script>' > > Since I am using texinfo 7 I dont need to mess with MathJax more than > what is done above. > > I dont know the purpose of that favicon (I can't find where it is > placed in the html, I just copied it from the texi2html init). favicon is the little icon browsers show for the website, often in the tab for the site. It's in doc/info/figures/favicon.ico. It's not needed if you don't want one. > Also, the manual.css is taken from the online version. I noticed that > the only difference from what I generate locally is the example pre > tag, which doesn't show up in the blue background. I probably will > change the manual.css to handle the class="example-preformatted" > instead of simply "example" > > Is that because I am using texinfo 7 and the online manual is currently > generated with an earlier version? I don't know much about manual.css. The current online manual was generated using texinfo 6.5, I think. It looks fine on a desktop but is really pretty bad when viewed on a mobile device like a phone or tablet, because some text shows up in a really tiny font. 6.8 and later fixes that. |