From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: org-mode table alignment options (siunitx S-column) Date: Tue, 16 Feb 2016 17:58:32 +0100 Message-ID: <87egccpp6v.fsf@nicolasgoaziou.fr> References: <56C11B7F.3050104@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49671) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aVivN-0006ra-N0 for emacs-orgmode@gnu.org; Tue, 16 Feb 2016 11:56:30 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aVivM-0004TF-Oj for emacs-orgmode@gnu.org; Tue, 16 Feb 2016 11:56:29 -0500 Received: from relay4-d.mail.gandi.net ([2001:4b98:c:538::196]:35006) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aVivM-0004TB-ID for emacs-orgmode@gnu.org; Tue, 16 Feb 2016 11:56:28 -0500 In-Reply-To: <56C11B7F.3050104@gmail.com> (Michael Giepen's message of "Mon, 15 Feb 2016 01:27:43 +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: Michael Giepen Cc: emacs-orgmode@gnu.org Hello, Michael Giepen writes: > However, with wider tables you have to put a lot of attributes and the > following implementation would be clearer if it would be more org-mode > like with the attributes inside the table. > > #+CAPTION: My caption > #+ATTR_LATEX: :align lS > | Column | Value | Value | Value | Value | Value | > | | | | | | | > | A | 2234.2 | 2234.2 | 2234.2 | 2234.2 | 2234.2 | > | B | 243.2345 | 243.2345 | 243.2345 | 243.2345 | 243.2345 | > | C | 2.03 | 2.03 | 2.03 | 2.03 | 2.03 | > | D | 4.0 | 4.0 | 4.0 | 4.0 | 4.0 | > > But only l, c, and r and numbers for width are recognised within < >, > the S not. > > Could this be expanded somehow to allow for any letter, or at least to > the ones that make sense? Org implements minimal alignment rules, but it does so across all major export back-ends. Introducing some new syntax here has at least 2 drawbacks: 1. It requires an implementation in every major back-ends, which may not be always possible (e.g., in LaTeX, another default package is required) 2. It may introduce some false positives (e.g., is "| |" an alignment cookie or a regular field?). I think #+ATTR_BACKEND: :align ... goes a long way towards removing these limitations, at least on the export side. Regards, -- Nicolas Goaziou