From: Dominik Schrempf <dominik.schrempf@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: LaTeX in HTML export [8.3.2 (release_8.3.2-380-g64aee4 @ /home/dominik/.emacs.d/org-mode/lisp/)]
Date: Fri, 11 Dec 2015 16:54:22 +0100 [thread overview]
Message-ID: <87oadx56c1.fsf@gmail.com> (raw)
In-Reply-To: <87zixhhw0v.fsf@gmx.us> (rasmus@gmx.us's message of "Fri, 11 Dec 2015 15:58:40 +0100")
Hi Rasmus,
thanks for your answer. I asked the people from MathJax and the problem
is HTML related. =<i= is interpreted as an HTML tag by the browser.
This behavior is well known and explained in the MathJax
Documentation.
http://docs.mathjax.org/en/latest/tex.html#tex-and-latex-in-html-documents
Maybe Org mode HTML export should take this into account, especially
because =<i= is used quite often? I understand if this is not feasible.
Thanks,
Dominik
On Fri, Dec 11 2015, Rasmus wrote:
> The following message is a courtesy copy of an article
> that has been posted to gmane.emacs.orgmode as well.
>
> Hi Dominik,
>
> Thanks for your report.
>
> Dominik Schrempf <dominik.schrempf@gmail.com> writes:
>
>> I am trying to export a LaTeX code block into HTML and have a problem
>> when using lower (<) signs (maybe it also happens with greater signs but
>> I did not check that).
>>
>> E.g., the following Org code leads to an error when viewing the HTML
>> file because the '<' sign is interpreted in a wrong way (I don't know
>> how but it seems to be interpreted as part of a tag) and MathJax does
>> not succeed then.
>
> Your example suggests it's an upstream bug or feature. Perhaps try:
>
> https://github.com/mathjax/MathJax/issues
>
> Thanks,
> Rasmus
next prev parent reply other threads:[~2015-12-11 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 13:45 Bug: LaTeX in HTML export [8.3.2 (release_8.3.2-380-g64aee4 @ /home/dominik/.emacs.d/org-mode/lisp/)] Dominik Schrempf
2015-12-11 14:58 ` Rasmus
2015-12-11 15:54 ` Dominik Schrempf [this message]
2015-12-11 17:42 ` Rasmus
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=87oadx56c1.fsf@gmail.com \
--to=dominik.schrempf@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).