unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: chad <yandros@gmail.com>
To: Cecilio Pardo <cpardo@imayhem.com>
Cc: emacs-devel@gnu.org
Subject: Re: Colorizing source code in Info manuals
Date: Wed, 11 Dec 2024 16:04:06 -0500	[thread overview]
Message-ID: <CAO2hHWa3regFV5QE_0hzu0-1m-nO-7X15MesjRwZn-K=B+Ttcg@mail.gmail.com> (raw)
In-Reply-To: <7cc30358-1412-4845-8f2d-efce17543cfd@imayhem.com>

[-- Attachment #1: Type: text/plain, Size: 1492 bytes --]

On Wed, Dec 11, 2024 at 5:41 AM Cecilio Pardo <cpardo@imayhem.com> wrote:

> On 11/12/2024 5:33, Richard Stallman wrote:
>
> >> Texinfo's HTML uses CSS, which I think emacs does not support.
> >
> > Indeeed, handling CSS would be a lot of additional work.
> >
> > Does HTML itself have any extensibility, any way to define (in effect)
> > macros, so that `<dfn>...</dfn>' could translate into `*<i>...</i>*'?
>
> No. We could use javascript for the browsers, and preprocess with lisp
> for emacs if we go that way, but it doesn't sound natural.
>

This is not quite correct; HTML has DIV and SPAN elements that can
attach arbitrary ID's to sections or spans of text in an html
document. This is _usually_ used for styling, via CSS, but it would be
easy to include CSS in the HTML output that makes <span
id="definition">code here</span> or <span className="definition">code
here</span> style the text in italics. This usage is not currently
common, but it was part of the original intended usage way-back-when,
and I don't know why it wouldn't still work.

It would also be pretty easy to add support for such "custom tags" to
eww's HTML renderer (shr.el, which seems to be not thoroughly
documented, at least in my current install). I admit that I'm not sure
why one might want to look at info manuals in HTML format inside
emacs, but if it's wanted, it shouldn't be difficult.

Apologies if I've added noise due to missing something in the thread.

~Chad

[-- Attachment #2: Type: text/html, Size: 2101 bytes --]

  reply	other threads:[~2024-12-11 21:04 UTC|newest]

Thread overview: 17+ 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 [this message]
2024-12-11  4:33         ` Richard Stallman
2024-12-11 11:01           ` Cecilio Pardo
2024-12-11 17:14             ` [External] : " Drew Adams
2024-12-06  7:38 ` Eli Zaretskii
2024-12-06  8:52   ` Cecilio Pardo
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

  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='CAO2hHWa3regFV5QE_0hzu0-1m-nO-7X15MesjRwZn-K=B+Ttcg@mail.gmail.com' \
    --to=yandros@gmail.com \
    --cc=cpardo@imayhem.com \
    --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 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).