ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Which table environment?
Date: Wed, 12 Jan 2011 11:23:45 +0100	[thread overview]
Message-ID: <699AFAE0-E8DB-4681-A0FE-F1F3CCCF7FBE@gmail.com> (raw)
In-Reply-To: <AANLkTi=3VPtMMpnUriNh2sUiQDojj6CJJgbqQ96ZPXBu@mail.gmail.com>


Am 11.01.2011 um 01:03 schrieb Felix Ingram:

> Hello all,
> 
> I've been playing with the various table environments but I thought
> I'd seek advice as to which would be the best for my requirements.
> 
> I need to be able to do the following:
> 
> - Repeating header row with coloured background and text (I can get
> this working with TABLE but not tabulate).

Tabulate supports background color for cells, Hans posted a example
last november.

Headers and footers are supported too, look for \starttabulatehead
and \starttabulatetail.

> - Multi-page tables (TABLE and tabulate are fine with these).
> - Insert images in a cell (TABLE seems to handle this better than tabulate).

Indeed.

> - Have rows that will split across pages - we will have large pieces
> of text and images which will end up being taller than the page.
> (tabulates paragraph support is the right sort of thing)

Correct, tabulate only feature.

> - Start next row on current page.

???

> - Include other tables, lists etc in a cell (this is a "nice to have"
> rather than a "must have")

TABLE

> The reason I need these various things is because Word acts this way
> and I need to produce something similar (until we can argue for a
> format change).

Use tabulate for text centric tables and TABLE for tables with a strict
layout and figures and other content (because you can set the cells
width and height).

> At the moment I'm leaning towards tabulate but I'm having issues with
> images and the headers. I'm using Mk IV (bonus question: as a newbie,
> should I just start with IV and ignore II? Or is II better for any
> particular reason?).


Use MkIV, the differences between both are not so big but for me there
are many minor things why i prefer MkIV over MkII.

Wolfgang

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


      reply	other threads:[~2011-01-12 10:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11  0:03 Felix Ingram
2011-01-12 10:23 ` Wolfgang Schuster [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=699AFAE0-E8DB-4681-A0FE-F1F3CCCF7FBE@gmail.com \
    --to=schuster.wolfgang@googlemail.com \
    --cc=ntg-context@ntg.nl \
    /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.
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 NNTP newsgroup(s).