emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Puneeth Chaganti <punchagan@gmail.com>
To: avdi@avdi.org
Cc: emacs-orgmode <emacs-orgmode@gnu.org>,
	Jambunathan K <kjambunathan@gmail.com>
Subject: Re: HTML Syntax Highlighting Questions
Date: Mon, 30 May 2011 10:17:38 +0530	[thread overview]
Message-ID: <BANLkTikoYPJ314S19VAHf_H3_+VfDrYqEg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikB5fYf+WDMR8YhntjN-t79Ba+JCQ@mail.gmail.com>

On Mon, May 30, 2011 at 7:55 AM, Avdi Grimm <avdi@avdi.org> wrote:
> 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?

I've some hackish code, which I use to publish my blog. It
essentially, looks at all the code blocks in the html output and
replaces them with Pygments output for them.  The code is here [1]


[1] https://github.com/punchagan/org-hyde/blob/master/org-hyde.el#L109

  parent reply	other threads:[~2011-05-30  4:48 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
2011-05-30  4:47     ` Puneeth Chaganti [this message]
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=BANLkTikoYPJ314S19VAHf_H3_+VfDrYqEg@mail.gmail.com \
    --to=punchagan@gmail.com \
    --cc=avdi@avdi.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=kjambunathan@gmail.com \


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