From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Michael Giepen <giepen.m@googlemail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-mode table alignment options (siunitx S-column)
Date: Tue, 16 Feb 2016 17:58:32 +0100 [thread overview]
Message-ID: <87egccpp6v.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <56C11B7F.3050104@gmail.com> (Michael Giepen's message of "Mon, 15 Feb 2016 01:27:43 +0100")
Hello,
Michael Giepen <giepen.m@googlemail.com> 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 |
> | <l> | <S> | <S> | <S> | <S> | <S> |
> | 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 "| <foo> |" 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
next prev parent reply other threads:[~2016-02-16 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 0:27 org-mode table alignment options (siunitx S-column) Michael Giepen
2016-02-16 16:58 ` Nicolas Goaziou [this message]
2016-02-16 19:55 ` Eric S Fraga
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=87egccpp6v.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=giepen.m@googlemail.com \
/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).