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: Sat, 5 Nov 2022 20:06:25 +0700	[thread overview]
Message-ID: <tk5n4j$140s$1@ciao.gmane.io> (raw)
In-Reply-To: <sjn2cn$1748$1@ciao.gmane.io>

This is a reminder of an old bug. From my point of view it is serious 
enough, but not release critical due to its age.

&<> characters must be escaped as HTML entities when LaTeX snippets and 
blocks are exported for MathJax

Form my year-old notes:
- =#+options: tex:verbatim= properly escapes symbols.
- There are functions that performs such replacement in ox-html and 
ox-odt, but `org-format-latex` resides in org.el, so some refactoring 
and backward compatibility stubs are necessary.

This thread was tracked at https://updates.orgmode.org for a minor fix 
of the manual.

On 07/10/2021 22:05, Max Nikulin wrote:
> On 07/10/2021 20:05, Timothy wrote:
>>> Org should rewrite < and > to &lt; and &gt; to avoid broken HTML, or 
>>> as < and  in general.
>>
>> I think we’ve drifted a bit to the differences in processing (where 
>> the `\( ... \)'
>> vs `$ ... $' comments are most pertinent), but as you say for valid 
>> HTML < and >
>> should be rewritten. I don’t think I’ve seen an issue because MathJax 
>> seems to
>> take care of it, but it looks like MathJax is also fine with &lt; and 
>> &rt;.
> 
> "<" and ">" characters are valid only markup elements in HTML (part of 
> tags, comments). MathJax interprets text content. Normally, to add text 
> "<" or ">", "&lt;" or "&gt;" should be used in HTML sources. Browsers 
> may pass "<" and ">" from source to text content if they are totally 
> confused by invalid markup that does not resemble tags or something 
> else. I do not think, it should be abused.
> 
> I cited MathJax docs just to show a temporary workaround till the bug 
> will be fixed in Org. It is quite strange that Org properly converts 
> "<>&" to entities in text but leaves them as is in math snippets. Unsure 
> whether git history might clarify some reasons of such behavior.





  parent reply	other threads:[~2022-11-05 13:07 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
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 [this message]
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:
  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='tk5n4j$140s$1@ciao.gmane.io' \
    --to=manikulin@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).