emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Denis Bitouzé" <public-dbitouze-39ZsbGIQGT5GWvitb5QawA@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: 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: Sun, 13 Sep 2015 22:47:32 +0200	[thread overview]
Message-ID: <87y4gat5az.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <m3io7e5anb.fsf@example.com> ("Denis \=\?utf-8\?Q\?Bitouz\=C3\=A9\?\= \=\?utf-8\?Q\?\=22's\?\= message of "Sun, 13 Sep 2015 22:26:00 +0200")

Denis Bitouzé <dbitouze-39ZsbGIQGT5GWvitb5QawA@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 &vert;, 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 &vert; over |, and so does markdown.

There are a few options available:

  1. Prefer | over &vert; in HTML
  2. Overwrite "vert" entity with a new one that would do 1. So
     basically, this is 1 but on your machine only.
  3. Use a new entity that becomes | when used in HTML export.



  reply	other threads:[~2015-09-13 20:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-12 14:02 Bug: \vert{} exported to markdown not as expected [8.3.1 (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)] Denis Bitouzé
2015-09-13 20:04 ` Nicolas Goaziou
     [not found]   ` <87bnd6ulv0.fsf-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org>
2015-09-13 20:26     ` Denis Bitouzé
2015-09-13 20:47       ` Nicolas Goaziou [this message]
2015-09-14  0:10         ` Charles C. Berry
     [not found]           ` <alpine.OSX.2.20.1509131701560.819-iDQ3frm8jJiryYnjg5slPZa4wMfmKMrbhPhL2mjWHbk@public.gmane.org>
2015-09-14  7:46             ` Denis Bitouzé
     [not found]         ` <87y4gat5az.fsf-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org>
2015-09-14  6:35           ` Denis Bitouzé
     [not found]             ` <1442212613.9320.TMDA@plane.gmane.org>
     [not found]               ` <1442212613.9320.TMDA-wOFGN7rlS/M9smdsby/KFg@public.gmane.org>
2015-09-14  7:10                 ` Please confirm your message Denis Bitouzé
     [not found]                   ` <1442214745.28220.TMDA@plane.gmane.org>
     [not found]                     ` <1442214745.28220.TMDA-wOFGN7rlS/M9smdsby/KFg@public.gmane.org>
2015-09-14  7:11                       ` Denis Bitouzé

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=87y4gat5az.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=public-dbitouze-39ZsbGIQGT5GWvitb5QawA@plane.gmane.org \
    --cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \


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