From: Xavier Garrido <xavier.garrido@gmail.com>
To: Ista Zahn <istazahn@gmail.com>,
Xavier Garrido <xavier.garrido@gmail.com>
Cc: Richard Lawrence <richard.lawrence@berkeley.edu>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Exporting LaTeX source blocks with HTML backend
Date: Tue, 04 Mar 2014 00:31:43 +0100 [thread overview]
Message-ID: <531510DF.70209@gmail.com> (raw)
In-Reply-To: <CA+vqiLEVAuJfX3HK1O0b99g+vwTYW8tayUYht5+rWhAJv87c_A@mail.gmail.com>
Hi Ista,
Le 03/03/2014 20:55, Ista Zahn a écrit :
> Hi Xavier,
>
> I think
>
> #+begin_src latex :results drawer :exports results
> \begin{align*}
> x&=x\\
> y&=y
> \end{align*}
> #+end_src
>
> will give both syntax highlighting (in the code block) as well as
> properly displayed equations in both latex and html export.
>
This one works. Thanks for your help.
Xavier
> Best,
> Ista
>
> On Mon, Mar 3, 2014 at 2:39 PM, Xavier Garrido <xavier.garrido@gmail.com> wrote:
>> Hi Richard,
>>
>> Le 03/03/2014 20:24, Richard Lawrence a écrit :
>>
>>>> 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 don't quite understand what you're looking for here. Are you wanting
>>> these blocks to be exported as source code? Or do you want them to be
>>> interpreted somehow?
>>
>>
>> I would like to get them interpreted as raw LaTeX code in such way MathJax
>> can reinterpret them as you said.
>>
>>
>>> Removing the BEGIN_SRC/END_SRC lines will just result in raw LaTeX code
>>> getting dumped into your HTML, and a browser won't know what to do with
>>> that (at least not without help...are you wanting MathJax to interpret
>>> it?).
>>>
>>>> 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
>>>
>>> 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.
>>
>>
>>
>>>
>>> If you are instead looking to get something in your HTML output that
>>> looks like the result of compiling the LaTeX code, I am not exactly sure
>>> how to accomplish this, but it looks like there is some useful
>>> information in the section "Math formatting in HTML export" in the Org
>>> manual about either using MathJax or preprocessing LaTeX code into
>>> images with dvipng.
>>
>>
>> Actually, I just want to get the LaTeX code translated into raw code. As I
>> wrote, there is one solution, pretty easy to implement and may be used by
>> most of the org users : write raw LaTeX inside org document and use MathJax
>> for example, to interpret it in a convenient way. It is going to work for
>> both exporter html and latex. The point here is that using raw LaTeX code
>> makes me lose the syntax highlighting which is really useful for debugging
>> long LaTeX equation.
>>
>> Cheers,
>> Xavier
>>
>>> Hope that helps,
>>> 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 23:31 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 [this message]
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=531510DF.70209@gmail.com \
--to=xavier.garrido@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=istazahn@gmail.com \
--cc=richard.lawrence@berkeley.edu \
/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).