all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Cecilio Pardo <cpardo@imayhem.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Colorizing source code in Info manuals
Date: Fri, 6 Dec 2024 09:52:41 +0100	[thread overview]
Message-ID: <18de1f26-7ae5-4155-bd34-4f2c98e82632@imayhem.com> (raw)
In-Reply-To: <86zfl9l0rj.fsf@gnu.org>

On 06/12/2024 8:38, Eli Zaretskii wrote:

> I'm not sure "is not going to add features like color to the Info
> format" is correct.  Texinfo does support syntax-highlighting of code
> snippets in HTML output (for now as an experimental feature), so it is
> not outlandish to assume something similar can be done for the Info
> format as well.

It says so in the texinfo manual:

      Can the Info format be extended to support fonts, colors or
      reflowable text?

      [...]

      Info's core purpose is to display documentation on text terminals.
      If you want more, you are recommended to use the HTML output from
      ‘texi2any’ instead.

Maybe they can add a 'subformat'.

> I think this should be discussed with the Texinfo developers, not
> here.  I can think about at least two possible ways of implementing
> this in Texinfo:
> 
>   . makeinfo could mark the code blocks with special markers, similar
>     to what it already does with image specs and indices
>   . makeinfo could produce ANSI color escape sequences in the Info
>     output, driven by the same syntax-highlighting machinery already
>     used for HTML

I'll take a look at what it does with images and take it to them. Will 
try to include a patch, but I can't really perl.



  reply	other threads:[~2024-12-06  8:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-05 22:06 Colorizing source code in Info manuals Cecilio Pardo
2024-12-05 22:33 ` Dr. Arne Babenhauserheide
2024-12-06  0:31   ` Arsen Arsenović
2024-12-06  8:39   ` Cecilio Pardo
2024-12-08  5:17     ` Richard Stallman
2024-12-08 18:08       ` Cecilio Pardo
2024-12-08 19:58         ` Björn Bidar
2024-12-11  4:33         ` Richard Stallman
2024-12-11 10:41           ` Cecilio Pardo
2024-12-11 21:04             ` chad
2024-12-11  4:33         ` Richard Stallman
2024-12-11 11:01           ` Cecilio Pardo
2024-12-11 17:14             ` [External] : " Drew Adams
2024-12-24 23:08           ` Cecilio Pardo
2024-12-26  4:30             ` Richard Stallman
2024-12-26  8:56               ` Cecilio Pardo
2024-12-28  4:34                 ` Richard Stallman
2024-12-06  7:38 ` Eli Zaretskii
2024-12-06  8:52   ` Cecilio Pardo [this message]
2024-12-06 11:42     ` Eli Zaretskii
2024-12-09  4:56 ` Richard Stallman

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=18de1f26-7ae5-4155-bd34-4f2c98e82632@imayhem.com \
    --to=cpardo@imayhem.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.