Hello,
Michael Giepen <giepe...@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
