Le 13/09/15 à 22h47, Nicolas Goaziou <m...@nicolasgoaziou.fr> a écrit :
> Denis Bitouzé <dbitouze-39zsbgiqgt5gwvitb5q...@public.gmane.org> 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
