Le 13/09/15 à 22h04, Nicolas Goaziou <m...@nicolasgoaziou.fr> a écrit :
> Hello, Hello, > dbito...@wanadoo.fr (Denis Bitouzé) writes: > >> The following file: >> >> #+NAME: test.org >> #+begin_src org >> Foo |bar_baz| >> >> Foo \vert{}bar\under{}baz\vert{} >> #+end_src >> >> is exported to markdown as follows: >> >> #+NAME: test.md >> #+begin_src markdown >> Foo |bar\_baz| >> >> Foo |bar_baz| >> #+end_src >> >> Whereas: >> >> - \under{} gives the expected underscore symbol (_), >> - \vert{} gives | instead of the expected pipe symbol (|). > > What is wrong with |? Doesn't Markdown accept HTML entities > anyway? The point is the following: the site where the .md file (exported from the .org file) will be used has this (maybe current) feature to be able to interpret strings such as: |REP_TO_COMMENT| Hence, I have to export "real" _ and |. 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 |. Regards. -- Denis