I'll agree with Daniel that sometimes, it's useful to have vertical
table separators. Here's how I kind-of do it:
| asdlfj | | alsjfdas |
|+---+--|
| alsdjf | | aqsljf |
| asdljf | | asldjf |
This is visible enough inside of org-mode and it yields a widish gap in
exp
I'll agree with Daniel that
sometimes, it's useful to have vertical table separators. Here's how I
kind-of do it:
| asdlfj | | alsjfdas |
|+---+--|
| alsdjf | | aqsljf |
| asdljf | | asldjf |
This is visible enough inside of org-mode and it yields a widish
gap in ex
I'll agree with Daniel that
sometimes, it's useful to have vertical table separators. Here's how I
kind-of do it:
| asdlfj | | alsjfdas |
|+---+--|
| alsdjf | | aqsljf |
| asdljf | | asldjf |
This is visible enough inside of org-mode and it yields a widish
gap in ex
On Apr 12, 2007, at 20:48, Daniel J. Sinder wrote:
I think rejecting vertical rules as a matter of style is a mistake.
Whether you consider org-mode tables to be a markup or a
spreadsheet, it's peers -- HTML, LaTeX, Gnumeric, Excel, etc. --
will all produce tables with vertical rules if asked
Matej Cepl wrote:
> To the presentation of tables I would strongly suggest reading
> http://tug.ctan.org/tex-archive/macros/latex/contrib/booktabs/booktabs.pdf
> -- whenever I broke rules set there, I regreted it later.
For publication quality tables, as per the above reference, I would
generally
On Apr 12, 2007, at 14:21, Matej Cepl wrote:
Carsten Dominik <[EMAIL PROTECTED]> writes:
I don't like the idea of another character having
special meaning in tables. We would have to find
a different way to specify this.
To the presentation of tables I would strongly suggest reading
http://
Carsten Dominik <[EMAIL PROTECTED]> writes:
> I don't like the idea of another character having
> special meaning in tables. We would have to find
> a different way to specify this.
To the presentation of tables I would strongly suggest reading
http://tug.ctan.org/tex-archive/macros/latex/contrib
