emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Inequalities in math blocks
Date: Tue, 12 Oct 2021 19:02:05 +0700	[thread overview]
Message-ID: <sk3tft$8lm$1@ciao.gmane.io> (raw)
In-Reply-To: <87sfx7kpx0.fsf@alphaville.usersys.redhat.com>

On 12/10/2021 08:11, Nick Dokos wrote:
> Rudolf Adamkovič writes:
>> Max Nikulin writes:
>>> Though I am a bit surprised that Org did not replace characters to
>>> &lt;  and &gt; during export. Perhaps, it is possible to define a
>>> filter.
>> That makes sense, and thank you for the explanation. Ignoring the dead
>> link in the Org manual, I wonder how this bug can even exist in Org
>> after 15+ years of development. Some people, including the author of
>> TeX himself, write TeX without unnecessary whitespace. Strange! Either
>> way, rearranging bullet points should never break math without any
>> visual sign inside of Emacs. Thus, this represents a bug in Org. R+
> No, it does not. Org mode just passes LaTeX directly to MathJax
> without changing anything. If you want to blame somebody, you can
> blame HTML for choosing < and > as its delimiters: see
>     http://docs.mathjax.org/en/latest/input/tex/html.html#html-special-characters

Nick, I am sorry, but I do not see your point. Do you know any reason 
why Org properly escapes "<>&" in text but transparently passes them to 
HTML inside LaTeX fragment? Does escaping them everywhere lead to problems?

 From the referenced document (I posted this link on 2021-10-03):

> you need to be careful that your mathematics doesn’t look like HTML tags
> to the browser, which parses the page before MathJax gets to see it.
> you can use the HTML entities &lt;, &gt; and &amp; to encode these
> characters so that the browser will not interpret them, but MathJax will.

I fail to see any reason to blame HTML. Any text markup language 
requires some easily typed special characters. Org has one set of them, 
HTML another one. Export backend should just respect delimeters of the 
target format.

I understand expectations and thus complains of Rudolf. In my opinion he 
has reasons to be disappointed (and maybe even angry to some degree). It 
looks like a bug in Org that should be fixed. Workarounds exist but Org 
should be more reliable.

  reply	other threads:[~2021-10-12 12:09 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-03 11:04 Inequalities in math blocks Rudolf Adamkovič
2021-10-03 12:19 ` Max Nikulin
2021-10-03 13:12   ` Timothy
2021-10-05  7:55     ` Rudolf Adamkovič
2021-10-05  7:58       ` Timothy
2021-10-05 12:19         ` Eric S Fraga
2021-10-05 12:00       ` Max Nikulin
2021-10-05 12:50         ` Rudolf Adamkovič
2021-10-03 13:14   ` Rudolf Adamkovič
2021-10-12  1:11     ` Nick Dokos
2021-10-12 12:02       ` Max Nikulin [this message]
2021-10-03 16:17   ` [PATCH] org-manual.org: Update links to MathJax docs Max Nikulin
2022-08-21  5:53     ` Ihor Radchenko
2022-08-21  6:20       ` Max Nikulin
2022-08-22  2:39         ` Ihor Radchenko
2022-08-22 14:52           ` Max Nikulin
2022-08-23  2:32             ` Update Woof! version at updates.orgmode.org? (was: [PATCH] org-manual.org: Update links to MathJax docs) Ihor Radchenko
2022-08-23 15:02               ` Update Woof! version at updates.orgmode.org? Max Nikulin
2022-09-01  9:07                 ` Bastien
2022-09-01  9:02               ` Bastien
2021-10-06  7:39 ` Inequalities in math blocks Rudolf Adamkovič
2021-10-07 11:30   ` Greg Minshall
2021-10-07 11:33     ` Timothy
2021-10-07 12:13       ` Greg Minshall
2021-10-07 12:53     ` Rudolf Adamkovič
2021-10-07 13:05       ` Timothy
2021-10-07 15:05         ` Max Nikulin
2021-10-07 19:48           ` Rudolf Adamkovič
2022-11-05 13:06           ` Max Nikulin
2022-11-06  3:05             ` [BUG] Escaping "<" and ">" inside math blocks when exporting to HTML/MathJax (was: Inequalities in math blocks) Ihor Radchenko
2021-10-07 19:25         ` Inequalities in math blocks Rudolf Adamkovič
2021-10-08 12:37       ` Greg Minshall

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:

  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='sk3tft$8lm$1@ciao.gmane.io' \
    --to=manikulin@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).