From: Bastien Guerry <bzg@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Philip Kaludercic <philipk@posteo.net>,
Jonas Bernoulli <jonas@bernoul.li>,
Greg Minshall <minshall@umich.edu>,
emacs-orgmode@gnu.org, flexibeast@gmail.com, hniksic@gmail.com,
Timothy <orgmode@tec.tecosaur.net>
Subject: Re: Htmlize support, maintenance, and Org mode
Date: Mon, 14 Aug 2023 18:20:39 +0200 [thread overview]
Message-ID: <87h6p1bnoo.fsf@bzg.fr> (raw)
In-Reply-To: <87a5utpudm.fsf@localhost> (Ihor Radchenko's message of "Mon, 14 Aug 2023 14:32:21 +0000")
Ihor Radchenko <yantar92@posteo.net> writes:
> That's what I meant. The latest thread named some issue with fine-tuning
> the output and never got any follow-up.
(Please ignore my suggestion to explore the htmlfontify.el scenario.)
>>> As for engrave-faces, it is working for both LaTeX and HTML export.
>>
>> Would that have the same issue has htmlize, that it copies the colours
>> from the currently active theme, causing issues when exporting a website
>> while a dark-theme is enabled?
>
> No. It can copy the current theme, but it is not the default. Instead,
> engrave-faces provides customization on how the faces should be
> re-mapped. Defaults are tuned to work for usual white backgrounds, but
> can be customized either using existing Emacs themes, or by hand,
> mapping Emacs faces to text colors and attributes.
It looks like engrave-faces already does a better job than htmlize.el,
and does it for LaTeX too, I see no drawback in using engrave-faces as
a replacement of htmlize.el. Are there any?
--
Bastien Guerry
next prev parent reply other threads:[~2023-08-14 16:21 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 8:17 [MAINTENANCE] Org orphanage? Ihor Radchenko
2022-11-21 11:02 ` Bastien
2022-11-21 11:53 ` Ihor Radchenko
2022-11-22 0:45 ` Alexis
2022-12-11 10:29 ` Ihor Radchenko
2022-12-29 16:13 ` Bastien
2022-12-31 12:31 ` Ihor Radchenko
2023-01-02 15:07 ` Bastien
2023-01-02 15:12 ` Ihor Radchenko
2023-01-02 15:28 ` Bastien
2023-01-03 10:45 ` Ihor Radchenko
2023-01-04 9:30 ` Bastien
2023-01-05 11:02 ` Ihor Radchenko
2023-01-05 11:30 ` Bastien
2023-01-06 1:54 ` Samuel Wales
2023-01-06 8:09 ` Greg Minshall
2023-01-06 8:23 ` Bastien Guerry
2023-01-06 16:51 ` Ihor Radchenko
2023-01-06 17:06 ` tomas
2023-01-07 10:07 ` Bastien
2023-01-07 10:19 ` Bastien Guerry
2023-02-04 13:57 ` Ihor Radchenko
2023-08-16 15:33 ` Jonas Bernoulli
2023-08-17 12:28 ` Ihor Radchenko
2023-07-31 11:13 ` Ihor Radchenko
2023-08-13 15:11 ` Jonas Bernoulli
2023-08-13 15:36 ` Htmlize support, maintenance, and Org mode (was: [MAINTENANCE] Org orphanage?) Ihor Radchenko
2023-08-14 1:30 ` Samuel Wales
2023-08-14 13:15 ` Jonas Bernoulli
2023-08-14 13:35 ` Ihor Radchenko
2023-08-14 16:17 ` Htmlize support, maintenance, and Org mode Bastien Guerry
2023-08-14 16:22 ` Ihor Radchenko
2023-08-14 16:30 ` Bastien Guerry
2023-08-15 10:21 ` Timothy
2023-08-14 13:58 ` Philip Kaludercic
2023-08-14 14:14 ` Ihor Radchenko
2023-08-14 14:18 ` Philip Kaludercic
2023-08-14 14:32 ` Ihor Radchenko
2023-08-14 16:20 ` Bastien Guerry [this message]
2023-08-14 16:24 ` Ihor Radchenko
2023-08-15 10:27 ` [MAINTENANCE] Org orphanage? Hrvoje Nikšić
2023-08-15 16:12 ` Ihor Radchenko
2023-08-20 20:41 ` Hrvoje Nikšić
2023-08-16 15:16 ` Jonas Bernoulli
2023-08-17 12:27 ` Ihor Radchenko
2023-08-17 13:41 ` Jonas Bernoulli
2023-08-17 15:08 ` Corwin Brust
2023-08-21 7:46 ` Ihor Radchenko
2023-08-24 18:22 ` Jonas Bernoulli
2023-08-25 10:07 ` Ihor Radchenko
2023-08-18 9:19 ` Ihor Radchenko
2023-08-18 13:32 ` Alexis
2023-08-22 15:13 ` Bastien Guerry
2023-08-24 17:49 ` Jonas Bernoulli
2023-08-24 18:24 ` Bastien Guerry
2022-11-21 22:19 ` Tim Cross
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6p1bnoo.fsf@bzg.fr \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=flexibeast@gmail.com \
--cc=hniksic@gmail.com \
--cc=jonas@bernoul.li \
--cc=minshall@umich.edu \
--cc=orgmode@tec.tecosaur.net \
--cc=philipk@posteo.net \
--cc=yantar92@posteo.net \
/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/org-mode.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).