From: Xavier Garrido <xavier.garrido@gmail.com>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Exporting LaTeX source blocks with HTML backend
Date: Mon, 03 Mar 2014 18:43:10 +0100 [thread overview]
Message-ID: <5314BF2E.9020102@gmail.com> (raw)
Dear Orgers,
I am facing one issue when I am exporting from orgmode to html. I like
to write LaTeX code within #+BEGIN_SRC latex ... #+END_SRC block mainly
to take benefit/advantage of the syntax highlighting (debugging long
LaTeX equations is "simpler"). The problem is that these code blocks are
not exported at all by the html export backend whereas the LaTeX backend
does. Of course, an easy solution will be to remove the
#+BEGIN_SRC/#+END_SRC lines and both latex and html exporters will just
do it right. But, as I said, syntax highlighting is really useful and I
can't imagine living without it.
I have tried different things from adding a "before parsing hook" which
delete lines containing #+BEGIN_SRC/#+END_SRC (then I get problem with
other source block such as 'sh' that I want to be exported to 'pre' code
in html) to trying to play with filters (so far, I do not get any
getting LaTeX source block when exporting to html).
As a summary I would like to do the following
#+BEGIN_SRC org
* Test LaTeX block
Syntax highlighting is always nice but the following block is not
exported in html. An option will be to remove the #+BEGIN_SRC
latex/#+END_SRC lines
#+BEGIN_SRC latex
\begin{align*}
x&=x\\
y&=y
\end{align*}
#+END_SRC
* Test shell block
Here, I would like to keep the following source block as it is to get
it exported properly by html backend (namely as <pre> code)
#+BEGIN_SRC sh
uname -a
#+END_SRC
#+END_SRC
Thanks for your help,
Xavier
next reply other threads:[~2014-03-03 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 17:43 Xavier Garrido [this message]
2014-03-03 19:24 ` Exporting LaTeX source blocks with HTML backend Richard Lawrence
2014-03-03 19:39 ` Xavier Garrido
2014-03-03 19:55 ` Ista Zahn
2014-03-03 23:31 ` Xavier Garrido
2014-03-07 21:37 ` Eric S Fraga
2014-03-03 20:54 ` Richard Lawrence
2014-03-03 23:33 ` Xavier Garrido
2014-03-08 11:39 ` 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=5314BF2E.9020102@gmail.com \
--to=xavier.garrido@gmail.com \
--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).