From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nathan Trapuzzano Subject: Re: Bug: Table export to [tc]sv doesn't convert \vert [7.8.11] Date: Wed, 02 Jan 2013 16:50:21 -0500 Message-ID: <878v8bm7vg.fsf@nbtrap.com> References: <20121225233220.03a42d24@nbtrap.com> <87sj6qkrd7.fsf@bzg.ath.cx> <20121229202531.3787d46d@nbtrap.com> <87r4m7ewyu.fsf@bzg.ath.cx> <20121230230104.3314d945@nbtrap.com> <87obhao9fa.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:52071) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TqYbq-0003LC-1Z for emacs-orgmode@gnu.org; Wed, 02 Jan 2013 19:24:37 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TqYbn-000167-3C for emacs-orgmode@gnu.org; Wed, 02 Jan 2013 19:24:33 -0500 Received: from oproxy9.bluehost.com ([69.89.24.6]:59884) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1TqYbm-00014D-PC for emacs-orgmode@gnu.org; Wed, 02 Jan 2013 19:24:31 -0500 In-Reply-To: <87obhao9fa.fsf@bzg.ath.cx> (Bastien's message of "Mon, 31 Dec 2012 10:30:49 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 Cc: emacs-orgmode@gnu.org Bastien writes: > Hi Nathan, > > Nathan Trapuzzano writes: > >> 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. > > As a start, you can look at the way org-e-*.el backend export tables, > (use `org-e-ascii-table-cell' as an entry point). What we need is a > callback function to convert entities in cells, in org-export.el. > > Since we already have org-entities, I would use it together with > `org-entity-get-representation' to convert entities from the \vert{} > representation to the "|" character (in the ASCII backend.) > >> 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. > > Better to rely on org-entities and the way entities are treated so far. I only recently started using org-mode, let alone looking at the source. I'll see what you mean if I get the time. >> 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. > > I would not take that route -- from experience, escaping espace > sequences can drive you mad, and all this is not intuitive for users. The problem with not escaping escape sequences is that there always ends up being some string of characters that cannot be represented. As for driving one mad, I think that "\\\\+vert" is much simpler to understand than "\\(\\b\\\\vert\\b\\|\\\\vert{}\\)", especially if the latter only applies when the row in which the sequence falls is not escaped as you describe below. > I would simply convert entities by default and use a special table > cookie in lines where you do not want the conversion to happen. > > For example: > > | Header 1 | Header 2 | > |----------+----------| > | \vert{} | ABC | > > => convert to "|" > > But: > > | | Header 1 | Header 2 | > |---+----------+----------| > | \ | \vert{} | ABC | > > Don't convert. The "\" char is free and a good choice here. This would apply the escape to the entire row. I supposed it's better than the way things are now, but it's still not a very good solution in my mind.