> On Jan 15, 2020, at 22:43, Patrice Dumas <pertu...@free.fr> wrote:
> 
> On Wed, Jan 15, 2020 at 09:12:15PM +0900, Jean-Christophe Helary wrote:
>>> 
>>> The Guix developers managed to implement syntax highlighting by
>>> post-processing the HTML.
>>> (https://lists.gnu.org/archive/html/bug-texinfo/2019-11/msg00004.html)
>> 
>> Wow, I just checked this page:
>> https://guix.gnu.org/manual/devel/en/html_node/Using-the-Configuration-System.html
>> 
>> and the source if full of css "hooks" even for the parens in the code...
>> 
>> What they do is interesting, and I guess some kind of postprocessing would 
>> be possible to achieve what I suggest, but instead of that, I'm guessing 
>> that just having texinfo add the css selectors would be easier.
> 
> There are already hooks to customize the HTML produced, but it requires
> knowing perl and digging into the HTML customization API which is not
> documented anywhere.

Are you talking about HTML.pm ?

>> Also, what's interesting with the current HTML export is that even though it 
>> is quite "old" in terms of standard (supposed to accept HTML 3.2 if I 
>> remember correctly ?) adding appropriate classes and IDs is just enough to 
>> access even bleeding edge CSS. Hence the idea of adding the appropriate 
>> "hooks" directly from texinfo.
> 
> Currently the default is 4.01 Transitional.  But there is a
> customization file to produce HTML 3.2 in tp/init/html32.pm.

The default is high enough that it allows for <div>, <span>, class and id. 
That's all we need to make good use of CSS selectors.


Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune



Reply via email to