emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nathan Trapuzzano <nbtrap@nbtrap.com>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Table export to [tc]sv doesn't convert \vert [7.8.11]
Date: Sun, 30 Dec 2012 23:01:04 -0500	[thread overview]
Message-ID: <20121230230104.3314d945@nbtrap.com> (raw)
In-Reply-To: <87r4m7ewyu.fsf@bzg.ath.cx>

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 :)
> 

  reply	other threads:[~2012-12-31  4:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-26  4:32 Bug: Table export to [tc]sv doesn't convert \vert [7.8.11] Nathan Trapuzzano
2012-12-28 17:26 ` Bastien
2012-12-30  1:25   ` Nathan Trapuzzano
2012-12-30  9:00     ` Bastien
2012-12-31  4:01       ` Nathan Trapuzzano [this message]
2012-12-31  9:30         ` Bastien
2013-01-02 21:50           ` Nathan Trapuzzano
2013-01-03  8:57             ` Bastien

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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=20121230230104.3314d945@nbtrap.com \
    --to=nbtrap@nbtrap.com \
    --cc=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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