From: Emmanuel Charpentier <emm.charpentier@free.fr>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Suggestion : Option enabling LaTeX blocks to non-latex exporters.
Date: Sun, 18 Jul 2021 14:24:54 +0200 [thread overview]
Message-ID: <27a07324dffd035a3c5978dbe81e82ff7fbc0c8b.camel@free.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]
Dear list,
"raw" LaTeX can already be successfully exported by some exporters :
both html and odt exporters can translate (a limited subset of) such
latex expressions in something palatable to their respective targets
(Mathjax and representation MathML respectively).
This does *not* apply to LaTeX marked as such. To be clear :
babble babble $\int_a^b f(x) dx$ noise noise
will export the math expression to html and odt (if tex:t or
tex:dvipng or tex:dvisvgm) ; on the other hand
babble babble @@latex:$\int_a^b f(x) dx$@@ noise noise
will not. Neither will :
#+latex: \[\Phi_{\mu, \sigma}(x) = \frac{e^-{\frac{(x-\mu)^2}{2\sigma^2}}}{\sigma\sqrt{2\pi}}\,.\]
nor :
#+begin_export latex
\[\Phi_{\mu, \sigma}(x) = \frac{e^-{\frac{(x-\mu)^2}{2\sigma^2}}}{\sigma\sqrt{2\pi}}\,.\]
#+end_export
This has an annoying consequence : a function cannot (easily) return a
LaTeX block. One can return a raw result, but this loses the link
between the function and its result(s).
John Kitchin has suggested
(https://lists.gnu.org/archive/html/emacs-orgmode/2021-07/msg00099.html)
to wrap raw latex code in a drawer ; this works, but I am unable to
understand how, and I do not know what are the consequences.
Having an option allowing latex code marked as such to be passed to
other exporters (possibly with conversion) would allow a "cleaner"
solution.
What do you think ?
--
Emmanuel Charpentier
[-- Attachment #2: Type: text/html, Size: 1963 bytes --]
next reply other threads:[~2021-07-18 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-18 12:24 Emmanuel Charpentier [this message]
2021-07-18 14:25 ` Suggestion : Option enabling LaTeX blocks to non-latex exporters Timothy
2021-07-18 17:10 ` Emmanuel Charpentier
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=27a07324dffd035a3c5978dbe81e82ff7fbc0c8b.camel@free.fr \
--to=emm.charpentier@free.fr \
--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).