[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] Bug: \vert{} exported to markdown not as expected [8.3.1 (8.3.1-
From: |
Denis Bitouzé |
Subject: |
Re: [O] Bug: \vert{} exported to markdown not as expected [8.3.1 (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)] |
Date: |
Mon, 14 Sep 2015 08:35:04 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
Le 13/09/15 à 22h47, Nicolas Goaziou <address@hidden> a écrit :
> Denis Bitouzé <address@hidden> writes:
>
>> 1. For _, \under{} is necessary since _ at the org mode level is
>> exported as \_.
>> 2. For |, source | could be okay. But I'd like to use strings as above
>> in tables and, AFAIK, the only way to have pipe symbols in a table at
>> the org mode level is to code them \vert{}. And that's the purpose
>> of my bug report, \vert{} is exported as |, not as "real" |.
>>
>> In other words, I was happy with \under{} that exports real _ and,
>> IMHO, \vert{} should do the same with |.
>
> Markdown export back-end use :html conventions to translate entities.
> For some reason, HTML prefers | over |, and so does markdown.
| and | are displayed the same way but can have different
"meanings".
> There are a few options available:
>
> 1. Prefer | over | in HTML
Maybe I'm wrong but wouldn't this break backward compatibility?
> 2. Overwrite "vert" entity with a new one that would do 1. So
> basically, this is 1 but on your machine only.
The feature I'm requesting may be useful to others.
> 3. Use a new entity that becomes | when used in HTML export.
It would be harmless.
> WDYT?
The 3rd option looks the best one to me.
Regards.
--
Denis