From mboxrd@z Thu Jan 1 00:00:00 1970 From: Subject: Re: How to escape characters in tables Date: Mon, 7 Mar 2011 11:45:57 -0600 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Return-path: Received: from [140.186.70.92] (port=51771 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PweVP-00037r-FJ for emacs-orgmode@gnu.org; Mon, 07 Mar 2011 12:46:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PweVO-0008Hv-3m for emacs-orgmode@gnu.org; Mon, 07 Mar 2011 12:46:03 -0500 Received: from mailout1-trp.thomsonreuters.com ([163.231.6.6]:17954) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PweVN-0008Gs-Vi for emacs-orgmode@gnu.org; Mon, 07 Mar 2011 12:46:02 -0500 In-Reply-To: Content-Language: en-US List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: camille.persson@gmail.com Cc: emacs-orgmode@gnu.org From: Camille persson > 2011/3/4 >> [...] here's a test case that shows my intent: >>=20 >> | foo | =3Dm/foo\vert{}foodfight/=3D | >>=20 >> The \vert{} seems not to work inside a =3D...=3D construction. Furtherm= ore, >> the =3D...=3D construction is problematic there because it conflicts wit= h >>the >> start-of-formula syntax. > =3D...=3D is used for code so it is printed as it written > You may use \texttt{} > | foo | \texttt{m\/foo\vert{}foodfight\/} | Unfortunately that doesn't work when exporting to HTML though, I assume it's for LaTeX export only? I'd suggest there are 3 things that need to be addressed/fixed in org-mode. First, the table-parser should respect =3D...=3D sections and skip over the= m, just like a C preprocessor respects double-quoted string sections. Second, there should be a way to indicate verbatim sections that doesn't conflict with formula syntax. Finally, there should be a way (e.g. \x{...}) to stick in a character by ASCII/Unicode number. This would help with several issues when a literal character is intended but it conflicts with a markup character. -- Ken Williams Senior Research Scientist Thomson Reuters http://labs.thomsonreuters.com