From: Rick Frankel <rick@rickster.com>
To: Kelvin Hu <ini.kelvin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Fwd: Question: how to disable htmlize during exporting?
Date: Tue, 25 Mar 2014 11:37:47 -0400 [thread overview]
Message-ID: <0cff8b6ef93ec2d99c7e2f38097a7b9e@mail.rickster.com> (raw)
In-Reply-To: <CAO61DjysZv=WrUV_vO2Wd_o=moE93Rkma0ofTQeHr4hXzcRnag@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 655 bytes --]
On 2014-03-25 08:29, Kelvin Hu wrote:
> 2014-03-25 16:25 GMT+08:00 Bastien <bzg@gnu.org>:
>
> I'd try to set `org-html-htmlize-output-type' to nil but I didn't
> test. If it does not work, this is a bug.
>
> Thanks for your reply, I have tried this approach, but it reports
> "error: (void function nil)".
> Per the definition in `ox-html.el', it must be either 'inline-css or
> 'css.
>
But it's an excellent idea. I have a patch to ox-html which will allow
ox-htmlize-output type to be set to `nil', to explicitly return plain
text.
I will push it to master tonight when i get out from behind the
firewall...
rick
P.S. Attached for review...
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Allow-disabling-of-htmlization-in-ox-html-export.patch --]
[-- Type: text/x-lisp; name=0001-Allow-disabling-of-htmlization-in-ox-html-export.patch, Size: 2327 bytes --]
From b49fa8b36b983f32ca9ff090eec0be7ff45a50c3 Mon Sep 17 00:00:00 2001
From: Rick Frankel <rick@rickster.com>
Date: Tue, 25 Mar 2014 11:27:07 -0400
Subject: [PATCH] Allow disabling of htmlization in ox-html export.
* lisp/ox-html.el (org-html-htmlize-output-type): Add `nil'
option (no htmlization).
(org-html-fontify-code): Return plain text if
`org-html-htmlize-output-type' is `nil'.
---
lisp/ox-html.el | 13 +++++++++----
1 file changed, 9 insertions(+), 4 deletions(-)
diff --git a/lisp/ox-html.el b/lisp/ox-html.el
index 52795a3..a843441 100644
--- a/lisp/ox-html.el
+++ b/lisp/ox-html.el
@@ -756,9 +756,10 @@ link's path."
(defcustom org-html-htmlize-output-type 'inline-css
"Output type to be used by htmlize when formatting code snippets.
-Choices are `css', to export the CSS selectors only, or `inline-css', to
-export the CSS attribute values inline in the HTML. We use as default
-`inline-css', in order to make the resulting HTML self-containing.
+Choices are `css' to export the CSS selectors only,`inline-css'
+to export the CSS attribute values inline in the HTML or `nil' to
+export plain text. We use as default `inline-css', in order to
+make the resulting HTML self-containing.
However, this will fail when using Emacs in batch mode for export, because
then no rich font definitions are in place. It will also not be good if
@@ -771,7 +772,7 @@ all the faces you are interested in are defined, for example by loading files
in all modes you want. Then, use the command
\\[org-html-htmlize-generate-css] to extract class definitions."
:group 'org-export-html
- :type '(choice (const css) (const inline-css)))
+ :type '(choice (const css) (const inline-css) (const nil)))
(defcustom org-html-htmlize-font-prefix "org-"
"The prefix for CSS class names for htmlize font specifications."
@@ -1894,6 +1895,10 @@ is the language used for CODE, as a string, or nil."
(message "Cannot fontify src block (htmlize.el >= 1.34 required)")
;; Simple transcoding.
(org-html-encode-plain-text code))
+ ;; Case 3: plain text explicitly set
+ ((not org-html-htmlize-output-type)
+ ;; Simple transcoding.
+ (org-html-encode-plain-text code))
(t
;; Map language
(setq lang (or (assoc-default lang org-src-lang-modes) lang))
--
1.8.0
next prev parent reply other threads:[~2014-03-25 15:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 3:33 Question: how to disable htmlize during exporting? Kelvin Hu
2014-03-25 8:25 ` Bastien
[not found] ` <CAO61DjxKttv80o3pMN3Z2ZNORDRYw5j=E_eKrT0wiGypdWdSxg@mail.gmail.com>
2014-03-25 12:29 ` Fwd: " Kelvin Hu
2014-03-25 15:37 ` Rick Frankel [this message]
2014-03-25 15:41 ` 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=0cff8b6ef93ec2d99c7e2f38097a7b9e@mail.rickster.com \
--to=rick@rickster.com \
--cc=emacs-orgmode@gnu.org \
--cc=ini.kelvin@gmail.com \
/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).