From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: What happens to org-export-with-LaTeX-fragments
Date: Tue, 14 May 2013 15:02:53 +0200 [thread overview]
Message-ID: <87li7hogsi.fsf@pank.eu> (raw)
In-Reply-To: m1vc6l7w7g.fsf@gmail.com
Hi Leo,
> I am upgrading to org 8 and cleaning up my init. There are two variables
> that aren't defined any more: org-export-with-LaTeX-fragments and
I'm looking at an "old" exporter and assume that you are interested in
MathJax and HTML. . .?
In any case, the source suggests that org-element only checks
:with-latex, which can be set 'globally' with org-export-with-latex (I
think). Also, it seems there might be a bug in the docstring as the
function below suggests it also support value dvipng and mathjax. But
I could be wrong.
Anyway, check out this function:
#+BEGIN_SRC emacs-lisp
;;;; Latex Fragment [snip from ox-html.el]
(defun org-html-latex-fragment (latex-fragment contents info)
"Transcode a LATEX-FRAGMENT object from Org to HTML.
CONTENTS is nil. INFO is a plist holding contextual information."
(let ((latex-frag (org-element-property :value latex-fragment))
(processing-type (plist-get info :with-latex)))
(case processing-type
((t mathjax)
(org-html-format-latex latex-frag 'mathjax))
(dvipng
(let* ((formula-link (org-html-format-latex
latex-frag processing-type)))
(when (and formula-link
(string-match "file:\\([^]]*\\)" formula-link))
(org-html-format-inline-image
(match-string 1 formula-link) info))))
(t latex-frag))))
#+END_SRC
> org-highlight-latex-fragments-and-specials.
This is improved through org-highlight-latex-and-related. Check it
out.
Hope it helps,
Rasmus
--
. . . Stallman was indeed the tallest possible mountain and by
standing on his shoulders you could see forever. . .
next prev parent reply other threads:[~2013-05-14 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 9:21 What happens to org-export-with-LaTeX-fragments Leo Liu
2013-05-14 13:02 ` Rasmus [this message]
2013-05-15 0:26 ` Leo Liu
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=87li7hogsi.fsf@pank.eu \
--to=rasmus@gmx.us \
--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).