emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Way to replace normal tabular env with booktabs?
Date: Thu, 12 Jan 2012 12:50:18 -0600	[thread overview]
Message-ID: <CA+M2ft9bEH07eJ1_k_z=3kJz3SZi=VLjNNtvHmY8D5kuw0bieQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]

Greetings,


I was using wikibooks for some formatting assistance on tables the other
day and ran into mention of the booktabs package in the "Professional
tables" section. [1] [2]

I really, really liked it's formatting, especially since one of my column
headers was a fraction. The standard tabular package places the \hlines
extremely close to the top and bottom of my header row vs., as the booktabs
package says, having extremely nice looking spacing for the table. I ended
up doing the table manually inside #+begin_latex block.

Would there be any way to specify that booktabs should be used? The
formatting is literally identical except for 1) including the booktabs
package and 2) using \toprule, \midrule and \bottomrule instead of \hlines.
In fact, even with booktabs included, if you use \hlines instead of the
booktab specific lines, you'll get a "regular" tabular table.

Any thoughts on this?


Best regards,
John

-----
[1] http://en.wikibooks.org/wiki/LaTeX/Tables#Professional_tables
[2] http://www.ctan.org/tex-archive/macros/latex/contrib/booktabs/

[-- Attachment #2: Type: text/html, Size: 1463 bytes --]

             reply	other threads:[~2012-01-12 18:50 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-12 18:50 John Hendy [this message]
2012-01-12 20:12 ` Way to replace normal tabular env with booktabs? Thomas S. Dye
2012-01-12 23:19   ` John Hendy
2012-01-13  0:01     ` Thomas S. Dye
2012-01-13 13:21       ` John Hendy
2012-01-13 14:52         ` Niels Giesen
2012-01-13 15:35           ` John Hendy
2012-01-13 15:39           ` Carsten Dominik
2012-01-13 15:48             ` John Hendy
2012-01-13 18:32               ` Daniel Bausch
2012-01-13 19:03                 ` John Hendy
2012-02-03 23:24             ` John Hendy
2012-02-04 15:54               ` Nicolas Goaziou
2012-02-08 13:17                 ` Niels Giesen
2012-02-08 22:32                   ` Nicolas Goaziou
2012-02-09 19:50                     ` John Hendy
2012-02-09 19:57                       ` Thomas S. Dye
2012-02-09 20:20                         ` John Hendy
2012-02-09 20:24                           ` Nick Dokos
2012-02-09 20:27                           ` Thomas S. Dye
2012-02-09 20:29                           ` Nick Dokos
2012-02-09 21:09                             ` John Hendy
2012-02-09 21:26                             ` John Hendy
2012-02-09 22:04                               ` Thomas S. Dye
2012-02-13 22:13                                 ` John Hendy

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='CA+M2ft9bEH07eJ1_k_z=3kJz3SZi=VLjNNtvHmY8D5kuw0bieQ@mail.gmail.com' \
    --to=jw.hendy@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).