emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: Yuchen Guo <yuchen@apvc.uk>, emacs-orgmode@gnu.org
Subject: Re: Hyphen after LaTeX fragments
Date: Tue, 14 Mar 2023 18:12:20 +0700	[thread overview]
Message-ID: <9a9f1d43-7d28-508e-1c75-7294fb4d8953@gmail.com> (raw)
In-Reply-To: <861qlr4xyq.fsf@lan>

On 14/03/2023 14:02, Yuchen Guo wrote:
> Sometimes I encounter such texts:
>     One of the useful features of a basis $B$ in an $n$-dimensional space
> When entered as-is in Org mode and exported to LaTeX, the string
> "$n$-dimensional" is exported as plain text, as
>     One of the useful features of a basis \(B\) in an \$n\$-dimensional space

I assume "\(n\)-dimensional".

> In cases such as "$n$;" and "$n$.", they are correctly exported as
> "\(n\);" and "\(n\).".
> So, are there any option that can be tweaked to export "$MATH$-text"
> correctly?

Consider "$M$" as deprecated. Balance of lightweight markup and 
heuristics to distinguish literal symbols and markup markers is quite 
subtle. Dash detection is broken for a long time despite the manual 
still says that it is supported:

Max Nikulin to emacs-orgmode. Re: [PATCH] Add support for $…$ latex 
fragments followed by a dash. Tue, 1 Feb 2022 21:26:50 +0700. 

That thread contains examples what may be false positives, e.g.

Max Nikulin to emacs-orgmode. Re: [PATCH] Add support for $…$ latex 
fragments followed by a dash. Sun, 30 Jan 2022 22:28:38 +0700. 

Another thread:

Timothy to emacs-orgmode… Re: Depreciating TeX-style LaTeX fragments 
(was: Org Syntax Specification) Sun, 16 Jan 2022 00:36:35 +0800. 

  parent reply	other threads:[~2023-03-14 11:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14  7:02 Hyphen after LaTeX fragments Yuchen Guo
2023-03-14  7:04 ` Dominik Schrempf
2023-03-14 11:12 ` Max Nikulin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-13 19:44 Yuchen Guo
2023-03-13 15:15 Yuchen Guo
2023-03-20  1:54 ` iemacs
2023-03-21 16:35   ` Rudolf Adamkovič
2023-03-21 16:39     ` Dominik Schrempf
2023-03-22 12:25       ` Ihor Radchenko
2023-03-22 12:35         ` Dominik Schrempf
2023-03-22 13:02           ` Ihor Radchenko
2023-03-21 17:22     ` Yuchen Guo
2023-03-22 12:36       ` Ihor Radchenko
2023-04-17 14:01         ` Ihor Radchenko
2023-04-17 15:29           ` Dominik Schrempf

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=9a9f1d43-7d28-508e-1c75-7294fb4d8953@gmail.com \
    --to=manikulin@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yuchen@apvc.uk \


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