From: Jambunathan K <kjambunathan@gmail.com>
To: Tim Hawes <hawest@anx.com>
Cc: emacs-orgmode Mode <emacs-orgmode@gnu.org>
Subject: Re: Cannot convert to Odt
Date: Thu, 11 Jul 2013 22:39:17 +0530 [thread overview]
Message-ID: <87vc4hja6a.fsf@gmail.com> (raw)
In-Reply-To: <87wqox2md9.fsf@anx.com> (Tim Hawes's message of "Thu, 11 Jul 2013 10:37:54 -0400")
Tim Hawes <hawest@anx.com> writes:
> The problem was a shell code fragment, the parser did not know what to
> do with:
> #+BEGIN_SRC sh
> nodaemon)
> nodaemon()
> ;;
> #+END_SRC
>
> Just making the code more comprehensible as shell code as thus:
>
> #+BEGIN_SRC sh
> case "$1" in
> ....
> nodaemon)
> nodaemon()
> ;;
> ....
> esac
> #+END_SRC
>
> or changing the code segment into EXAMPLE instead, fixes it. It converts
> under 7.8.11 and 8.0.5
I don't use Org-mode or Babel myself. I don't understand shell code.
Different backends use different engines for colorizing source blocks.
ODT uses htmlfontify.
HTML uses htmlize.
LaTeX probably relies on TeX packages like minted etc.
I suspect the problem could be in htmlfontify library or the exporter
interfaces with it. If you could post a complete minimal snippet by
removing ellipses etc., I can do some post-mortem and narrow the issue
further.
You can turn off the colors on source blocks by customizing,
M-x customize-variable RET org-odt-fontify-srcblocks RET
So, instead of switching to EXAMPLE blocks you can just turn off
colorization and see whether problem is reproducible. This is a sure
proof that there is something amiss in htmlfontify.el or how the expoter
interfaces with it.
next prev parent reply other threads:[~2013-07-11 17:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 17:55 Cannot convert to Odt Tim Hawes
2013-07-10 18:11 ` Jambunathan K
2013-07-10 21:54 ` Tim Hawes
2013-07-11 2:32 ` Jambunathan K
2013-07-11 14:37 ` Tim Hawes
2013-07-11 17:09 ` Jambunathan K [this message]
2013-07-10 18:38 ` Eric S Fraga
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=87vc4hja6a.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=hawest@anx.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).