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: Thu, 7 Oct 2021 22:05:57 +0700	[thread overview]
Message-ID: <sjn2cn$1748$1@ciao.gmane.io> (raw)
In-Reply-To: <874k9tdlto.fsf@gmail.com>

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.

On 06/10/2021 14:39, Rudolf Adamkovič wrote
> I wrote the following: "[…] every term $t\in{}q$ with $idf(t)>c$ for
> some constant $c$ […]", and the "idf(t) > c" part got exported as
> "idf(t)". I cannot fix the paper at this point. Uh-oh!

If you submitted HTML file, you might suggest to open sources to make it 
obvious that the mistake was not intentional.

"$idf(t)>c$" means "i*d*f(t) > c". A bit more markup required to make 
"idf" typed in straight font instead of italics and to avoid additional 
space between characters.

It is matter of taste, but "{}" after "\in" looks a bit strange for me. 
"$t\in q$ is even shorter, "$t \in q$", having the same length, is more 
readable from my point of view.

  reply	other threads:[~2021-10-07 15:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-03 11:04 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
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 [this message]
2021-10-07 19:48           ` Rudolf Adamkovič
2021-10-07 19:25         ` 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='sjn2cn$1748$1@ciao.gmane.io' \
    --to=manikulin@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --subject='Re: Inequalities in math blocks' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this 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).