From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nathan Trapuzzano <nbtrap@nbtrap.com>
Subject: Re: Bug: Table export to [tc]sv doesn't convert \vert [7.8.11]
Date: Sun, 30 Dec 2012 23:01:04 -0500
Message-ID: <20121230230104.3314d945@nbtrap.com>
References: <20121225233220.03a42d24@nbtrap.com> <87sj6qkrd7.fsf@bzg.ath.cx>
	<20121229202531.3787d46d@nbtrap.com> <87r4m7ewyu.fsf@bzg.ath.cx>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([208.118.235.92]:54073)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <nbtrap@nbtrap.com>) id 1TpWkQ-0007Ov-KY
	for emacs-orgmode@gnu.org; Sun, 30 Dec 2012 23:13:13 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <nbtrap@nbtrap.com>) id 1TpWkN-0006D0-OB
	for emacs-orgmode@gnu.org; Sun, 30 Dec 2012 23:13:10 -0500
Received: from oproxy5-pub.bluehost.com ([67.222.38.55]:47614)
	by eggs.gnu.org with smtp (Exim 4.71)
	(envelope-from <nbtrap@nbtrap.com>) id 1TpWZ9-0003dn-BL
	for emacs-orgmode@gnu.org; Sun, 30 Dec 2012 23:01:31 -0500
In-Reply-To: <87r4m7ewyu.fsf@bzg.ath.cx>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org

Of course the particular implementation will have to be seen before it
can be accepted, but I'd like to get the spec accepted (provisionally)
before setting to work on it.

Here's what I propose:

1. Do away with \vert{} entirely, leaving just \vert as an escape
sequence standing for |, no matter where it appears. \vert{}
unnecesarily complicates things, in my opinion.

2. The escape sequence must itself be escapable, wherefore I propose
to give the backslash special meaning in front of the string
"vert". Specifically:

  a. An even number of consecutive backslashes followed by "vert"
  stands for that number of backslashes divided by two followed by
  "vert".

  b. An odd number of consecutive backslashes followed by "vert"
  stands for that many backslashes integer-divided by two, followed by
  "|".

For example, "\vert" exports to "|", "\\vert" to "\vert", "\\\vert" to
"\|", "\\\\vert" to "\\vert", and so on. Obviously, upon importing,
the reverse of the above will be carried out.

Nathan

On Sun, 30 Dec 2012 10:00:09 +0100
Bastien <bzg@altern.org> wrote:

> Hi Nathan,
> 
> Nathan Trapuzzano <nbtrap@nbtrap.com> writes:
> 
> > Thanks Bastien. I agree that we need a more general fix for \vert escapes
> > for exports to all formats. Unfortunately, the best way of going about it
> > (in my opinion) would not be backwards compatible.
> 
> Hopefully we can fix this while working on Org 8.0, which greatest
> feature will be the new exporter.  I expect everyone to expect this
> exporter can do miracles, even for such details.
> 
> > I'd offer the patch myself if I knew it would be accepted on the master
> > branch, so I will live with it the way it is until a solution is proposed.
> 
> We cannot decide whether the patch will be accepted until we see it :)
>