Re: The less ambiguous math delimiters in tables

[Max Nikulin <manikulin@gmail.com>]

On 31/12/2024 20:32, Ihor Radchenko wrote:
> | $10 | foo | $\alpha$ |

pandoc result matches my expectation:

\$10 & foo & \(\alpha\) \\

> | =10+20 | 30 | =foo= |

I found significantly more convincing cases with current parser when 
emphasis end marker accidentally appears in the middle of a link.

=something in a table looks like a formula imported from a spreadsheet. 
In the case of "native" Org table, this form is unlikely for input of 
some code block, so zero-width space may be used.

I admit that changing parser is not an easy task and I am aware that 
Nicolas is strongly if favor of current approach.

Nicolas Goaziou. c47b535bb origin/main org-element: Remove dependency on 
‘org-emphasis-regexp-components’
Thu, 18 Nov 2021 13:35:19 +0100.
<https://list.orgmode.org/87y25l8wvs.fsf@nicolasgoaziou.fr/>
> I disagree. Priority should be given to the first object being started.
> This is, IMO, the only sane way to handle syntax.

Nicolas Goaziou. org parser and priorities of inline elements.
Sat, 27 Nov 2021 20:02:31 +0100.
<https://list.orgmode.org/87mtlppgl4.fsf@nicolasgoaziou.fr/>
> I don't see any incentive to change the order objects are parsed, once
> you know how Org does it. This is just a red herring. What is useful,
> however, is to fontify them the way Org sees them.