From: Jambunathan K <kjambunathan@gmail.com>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: [odt] htmlfontify + Support for src blockfontification
Date: Fri, 19 Aug 2011 18:01:45 +0530 [thread overview]
Message-ID: <81ei0hk2fi.fsf@gmail.com> (raw)
In-Reply-To: <87bovllmot.fsf@gnu.org> (Bastien's message of "Fri, 19 Aug 2011 12:28:50 +0200")
Bastien <bzg@altern.org> writes:
> Hi Jambunathan,
>
> I see this addition in one of the latest commit:
>
> +(defcustom org-export-odt-use-htmlfontify t
> + "Specify whether or not source blocks need to be fontified.
> +Turn this option on if you want to colorize the source code
> +blocks in the exported file. For colorization to work, you need
> +to make available an enhanced version of `htmlfontify' library."
>
> For now, the correct default value is `nil', otherwise users will
> encounter problems.
No. There is an in-built deprecation as below:
#+begin_src emacs-lisp
(if (and org-export-odt-use-htmlfontify
(or (featurep 'htmlfontify) (require 'htmlfontify))
(fboundp 'htmlfontify-string))
...)
#+end_src
htmlfontify-string is a function that is available only in the enhanced
version of htmlfontify.
> Also, this change only make sense when the enhanced version of
> htmlfontify.el is publicly available, so that we can point at a
> URL. I guess this will be the case soon :)
--
next prev parent reply other threads:[~2011-08-19 12:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 20:36 [odt] htmlfontify + Support for src blockfontification Jambunathan K
2011-08-15 21:55 ` suvayu ali
2011-08-17 9:59 ` Bastien
2011-08-18 18:50 ` Jambunathan K
2011-08-18 18:57 ` Achim Gratz
2011-08-18 20:55 ` Jambunathan K
2011-08-18 23:10 ` suvayu ali
2011-08-19 7:31 ` Bastien
2011-08-19 8:22 ` Jambunathan K
2011-08-19 9:50 ` Bastien
2011-08-19 12:26 ` Jambunathan K
2011-08-19 12:49 ` Jambunathan K
2011-08-19 21:48 ` Bastien
2011-08-19 10:28 ` Bastien
2011-08-19 12:31 ` Jambunathan K [this message]
2011-08-19 20:20 ` Bastien
2011-08-19 10:31 ` Bastien
2011-08-19 12:13 ` Jambunathan K
2011-08-19 20:15 ` 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=81ei0hk2fi.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=bzg@altern.org \
--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).