From: Eric Schulte <eric.schulte@gmx.com>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-mime-htmlize and org-preview-latex-fragment
Date: Mon, 26 Mar 2012 07:31:19 -0400 [thread overview]
Message-ID: <878vinr2mg.fsf@gmx.com> (raw)
In-Reply-To: 87limsdzrl.fsf@mat.ucm.es
Uwe Brauer <oub@mat.ucm.es> writes:
>>> On Thu, 22 Mar 2012 23:34:08 +0100, Uwe Brauer <oub@mat.ucm.es> wrote:
>
>
> > Now org-mime-htmlize allows me to htmlize a message buffer
> > but seems not to work with org-preview-latex-fragment
> > either the png is not exported or I obtain an error message
> > of the sort:
>
> > Unknown conversion type nil for latex fragments.
> I am very confused the code in question contains a line of
> the sort:
> (org-export-with-LaTeX-fragments "dvipng")
>
> Uwe Brauer
> So the functionality seems to be implemented?
>
This functionality certainly used to work (and was one of my main
reasons for using org-mime-htmlize). There is a new error in the
`org-export-string' function when `org-export-with-LaTeX-fragments' is
set to "dvipng" which is causing export to fail. To exercise this bug
run the following elisp snippet.
(let ((org-export-with-LaTeX-fragments "dvipng"))
(org-export-string "A fraction $\\frac{1}{2}$." 'html "/tmp/"))
Which throws the following error.
org-format-latex: Unknown conversion type nil for latex fragments
Once this bug is fixed the use of LaTeX to generated inline images with
Org-mime should work once again.
Best,
--
Eric Schulte
http://cs.unm.edu/~eschulte/
next prev parent reply other threads:[~2012-03-26 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 22:34 org-mime-htmlize and org-preview-latex-fragment Uwe Brauer
2012-03-22 22:41 ` Uwe Brauer
2012-03-26 11:31 ` Eric Schulte [this message]
2012-03-27 9:57 ` Uwe Brauer
2012-03-27 10:22 ` Bastien
2012-03-27 10:34 ` Uwe Brauer
2012-03-27 10:39 ` Eric Schulte
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=878vinr2mg.fsf@gmx.com \
--to=eric.schulte@gmx.com \
--cc=emacs-orgmode@gnu.org \
--cc=oub@mat.ucm.es \
/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).