emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: avdi@avdi.org
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: HTML Syntax Highlighting Questions
Date: Mon, 30 May 2011 08:50:14 +0530	[thread overview]
Message-ID: <81pqn0q3gx.fsf@gmail.com> (raw)
In-Reply-To: <BANLkTikB5fYf+WDMR8YhntjN-t79Ba+JCQ@mail.gmail.com> (Avdi Grimm's message of "Sun, 29 May 2011 22:25:31 -0400")

Avdi Grimm <avdi@avdi.org> writes:

> On Sun, May 29, 2011 at 9:32 PM, Jambunathan K <kjambunathan@gmail.com> wrote:
>> Let me guess - It is either htmlize not being in your load path during
>> the batch run or font lock being not being explicity turned on during
>> the batch run or font-locking simply not making sense during batch
>> mode. Ultimately htmlize or for that matter htmlfontify seem to depend
>> on the fontification done by the fontification engine.
> Hm. Bonus question, then: source code highlighting via Pygments works
> great with LaTeX export and the "minted" package. How hard would it be
> to use Pygments instead of htmlize/htmlfontify for HTML-exported
> syntax highlighting?
> ...and who do I need to buy beer for to make this happen, since I
> don't have time to do it myself?

May be you could buy yourself a beer.

AFAICS, htmlize generates the css based on face attributes. I am sure
you could improve the results by customizing your face definitions -
font-lock-keyword-face, font-lock-comment-face etc etc.

As someone who is authoring a book you requirements could be
stringent. May be you use latex for producing book digitally and html
for getting the word out and striving to have similar visual effects on
both the mediums.

Jambunathan K.

  reply	other threads:[~2011-05-30  3:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-30  0:50 HTML Syntax Highlighting Questions Avdi Grimm
2011-05-30  1:32 ` Jambunathan K
2011-05-30  2:25   ` Avdi Grimm
2011-05-30  3:20     ` Jambunathan K [this message]
2011-05-30  4:47     ` Puneeth Chaganti
2011-06-09  1:45 ` Avdi Grimm

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:

  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=81pqn0q3gx.fsf@gmail.com \
    --to=kjambunathan@gmail.com \
    --cc=avdi@avdi.org \
    --cc=emacs-orgmode@gnu.org \


* 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


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).