emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: emacs-orgmode@gnu.org
Subject: Re: Documentation references to htmlize and htmlize vs. htmlfontify
Date: Mon, 08 Jan 2018 15:57:37 +0100	[thread overview]
Message-ID: <874lnw5rfi.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <878td8beaw.fsf@passepartout.tim-landscheidt.de> (Tim Landscheidt's message of "Mon, 08 Jan 2018 14:44:39 +0000")

Hello,

Tim Landscheidt <tim@tim-landscheidt.de> writes:

> Finally, Emacs already ships with htmlfontify.  On (non-Org)
> files, I see small, but not significant differences between
> it and htmlize.  Are there features that only htmlize of-
> fers?  Otherwise it would be very convenient to replace
> calls to htmlize with a wrapper that tests if the user set
> some configurable variable org-htmlize-function (and calls
> that), otherwise tries to load htmlize and use that, and
> falls back to using htmlfontify.  Glancing at the code, org-
> mode seems to use htmlize-region (with (point-min) (point-
> max), but on narrowed buffers) which htmlfontify does not
> offer, but it is unclear to me whether that would kill 100 %
> of all use cases or only some.  (If it works out of the box
> with htmlfontify for the most common ones, IMHO that would
> be preferable to the current situation where it does not
> work at all unless one installs htmlize.)

FWIW, I'm in favour of replacing entirely htmlize with htmlfontify,
since the latter is bundled with Emacs.

Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2018-01-08 14:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08 14:44 Documentation references to htmlize and htmlize vs. htmlfontify Tim Landscheidt
2018-01-08 14:57 ` Nicolas Goaziou [this message]
2018-01-08 15:53   ` Kaushal Modi
2018-04-26 23:34     ` Bastien

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=874lnw5rfi.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@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/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).