emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: "Rudolf Adamkovič" <salutis@me.com>
Cc: Max Nikulin <manikulin@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: [PATCH v2] org-manual.org: $n$-th is not math
Date: Sun, 19 Mar 2023 11:24:53 +0000	[thread overview]
Message-ID: <87zg89ugoq.fsf@localhost> (raw)
In-Reply-To: <m23561xakz.fsf@me.com>

Rudolf Adamkovič <salutis@me.com> writes:

> The attempts were always rejected.  So, just a "bummer".  :)

As I said in the linked message, supporting "-" will not solve the basic
issue, which is with the Org syntax not being LaTeX. Intra-word markup,
including $...$, requires workarounds. It is the trade-off we have to


>>>   The problem with parsing is more than just supporting $i$-th and
>>>   similar. For example, AMS style guide explicitly advises against using
>>>   $i$-th in favour of $i$th [1]:
>>>       Do not hyphenate “th” expressions: xth, not x-th or xth .
>>>   We can theoretically make a change to support "-", but then it will be
>>>   logical to support $i$th as well. (If we don't some users will still be
>>>   confused after trying to write $i$th and then not getting the expected
>>>   results). In this question, it would make sense to implement
>>>   all-or-everything approach. Otherwise, confusion (like raised in this
>>>   thread) will be inevitable.
>>>   However, from point of view of Org mode parser, supporting $i$th is a
>>>   nightmare.  Remember that Org mode is _not_ LaTeX and we have to support
>>>   a lot more frivolous syntax (even in LaTeX, runaway $ is often a source
>>>   of cryptic compilation errors). Currently, we _must_ rely on heuristics
>>>   to determine $$-style latex fragments. I do not know any way to support
>>>   $$ syntax without creating deviations from LaTeX. Extending the
>>>   heuristics will not resolve the underlying ambiguity of $$ syntax, just
>>>   hide it within even more obscure cases.

Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

  reply	other threads:[~2023-03-19 11:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 13:32 [PATCH] org-manual.org: $n$-th is not math Max Nikulin
2023-03-15 14:01 ` Loris Bennett
2023-03-15 17:25 ` Rudolf Adamkovič
2023-03-17 12:13   ` [PATCH v2] " Max Nikulin
2023-03-18 12:21     ` Ihor Radchenko
2023-03-19 11:08     ` Rudolf Adamkovič
2023-03-19 11:24       ` Ihor Radchenko [this message]
2023-03-19 15:18       ` Max Nikulin
2023-03-21 16:38         ` Rudolf Adamkovič
2023-03-22 11:47           ` Max Nikulin
2023-03-22 12:37           ` Timothy
2023-03-22 17:17             ` Rudolf Adamkovič
2023-03-23 12:03               ` Ihor Radchenko
2023-03-23 21:51                 ` Rudolf Adamkovič

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=87zg89ugoq.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=manikulin@gmail.com \
    --cc=salutis@me.com \


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