From: Patrice Dumas <pertusus@free.fr>
To: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
Cc: Texinfo Help <help-texinfo@gnu.org>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: html manual +css
Date: Wed, 15 Jan 2020 15:18:13 +0100 [thread overview]
Message-ID: <20200115141813.GL1435@free.fr> (raw)
In-Reply-To: <25F7C4CF-2B56-439B-BB23-54C718498D0E@gmail.com>
On Wed, Jan 15, 2020 at 10:52:06PM +0900, Jean-Christophe Helary wrote:
>
>
> > On Jan 15, 2020, at 22:43, Patrice Dumas <pertusus@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 ?
Yes.
--
Pat
prev parent reply other threads:[~2020-01-15 14:18 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 13:49 html manual +css Jean-Christophe Helary
2017-06-02 14:28 ` Paul Eggert
2017-06-02 14:45 ` Jean-Christophe Helary
2017-06-02 14:56 ` Jean-Christophe Helary
2017-06-02 15:14 ` Yuri Khan
2017-06-02 15:22 ` Eli Zaretskii
2017-06-02 15:29 ` Jean-Christophe Helary
2017-06-05 14:44 ` Jean-Christophe Helary
2017-06-06 22:41 ` Richard Stallman
2017-06-06 23:47 ` Jean-Christophe Helary
2017-06-07 14:27 ` Jean-Christophe Helary
2019-12-23 16:54 ` Jean-Christophe Helary
[not found] ` <jwvr20v6jug.fsf-monnier+emacs@gnu.org>
2019-12-24 9:06 ` Jean-Christophe Helary
2019-12-24 14:37 ` Jean-Christophe Helary
2019-12-24 14:43 ` Jean-Christophe Helary
2019-12-25 22:03 ` Stefan Monnier
2019-12-26 0:08 ` Jean-Christophe Helary
2019-12-26 14:09 ` Jean-Christophe Helary
2019-12-26 14:45 ` Stefan Monnier
2019-12-26 15:08 ` Jean-Christophe Helary
2019-12-26 15:22 ` Jean-Christophe Helary
2019-12-26 15:50 ` Stefan Monnier
2019-12-26 16:27 ` Yuri Khan
2019-12-26 18:17 ` Stefan Monnier
2019-12-26 16:53 ` Jean-Christophe Helary
2019-12-30 11:53 ` Jean-Christophe Helary
2020-01-15 11:20 ` Gavin Smith
2020-01-15 12:12 ` Jean-Christophe Helary
2020-01-15 13:43 ` Patrice Dumas
2020-01-15 13:52 ` Jean-Christophe Helary
2020-01-15 14:18 ` Patrice Dumas [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200115141813.GL1435@free.fr \
--to=pertusus@free.fr \
--cc=emacs-devel@gnu.org \
--cc=help-texinfo@gnu.org \
--cc=jean.christophe.helary@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).