> On Jun 8, 2017, at 23:59, Eli Zaretskii <[email protected]> wrote: > >>> I'm currently checking >>> /usr/local/Cellar/texinfo/6.3/share/texinfo/Texinfo/Convert/HTML.pm >>> to see what could be done in this area. >> >> Well, this is *way* beyond my comfort zone :) >> >> I've found the <dl> for function definitions (line 4280) but I have no idea >> how the rest is processed... >> >> For ex, I can't seem to find how @result{} is transformed into ⇒ ... > > In case you didn't already, please read the chapters "'texi2any': The > Generic Translator for Texinfo" and "Generating HTML". These describe > various details about the translator's internals, and also document > all the customization variables it supports. It's possible that the > answer for your questions is there.
Thank you Eli. I did take a look but I'm not familiar enough with the subject to understand everything. I'll take more time to read the relevant sections again later. Right now I'm testing the CSS I wrote on the Elisp reference, there are issues with the underlying texi code (mostly related to @example/@group sections) and how they are rendered in HTML but I'll just put that on a memo to work on later. I'll then check it with the intro, the emacs manual and the other manuals. And when I have something that I'm happy with will send it to emacs-devel. As I wrote earlier on emacs-devel, there seems to be a lot of areas when the HTML output could be improved. If that can be done with customization variables that would be great. Jean-Christophe
