From: Richard Lawrence <richard.lawrence@berkeley.edu>
To: Xavier Garrido <xavier.garrido@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Exporting LaTeX source blocks with HTML backend
Date: Mon, 03 Mar 2014 12:54:32 -0800 [thread overview]
Message-ID: <87ha7fovef.fsf@berkeley.edu> (raw)
In-Reply-To: <5314DA7A.7030703@gmail.com>
Xavier Garrido <xavier.garrido@gmail.com> writes:
>>> #+BEGIN_SRC latex
>>> \begin{align*}
>>> x&=x\\
>>> y&=y
>>> \end{align*}
>>> #+END_SRC
>> When I export this using the HTML exporter, the LaTeX code is wrapped in
>> a <div> with class="org-src-container", and the actual code appears
>> inside a <pre> tag. Is this the behavior you see? Is that not what you
>> want?
> In my case, the code is not even wrapped into org-src-container class,
> it just does not appear at all.
Hmm. If Ista's solution doesn't work for you, you may want to look into
why this is happening. Maybe you have a variable or option set
somewhere that is suppressing export of these blocks for some reason. I
am using the "maint" version of the exporter (8.2.5h) and I don't use
HTML export much, so I am pretty sure what I see is the current default
behavior.
Best,
Richard
(If possible, please encrypt your reply to me using my PGP key:
Key ID: CF6FA646
Fingerprint: 9969 43E1 CF6F A646.
See http://www.ocf.berkeley.edu/~rwl/encryption.html for more information.)
next prev parent reply other threads:[~2014-03-03 20:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 17:43 Exporting LaTeX source blocks with HTML backend Xavier Garrido
2014-03-03 19:24 ` 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 [this message]
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=87ha7fovef.fsf@berkeley.edu \
--to=richard.lawrence@berkeley.edu \
--cc=emacs-orgmode@gnu.org \
--cc=xavier.garrido@gmail.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).