ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>
To: ntg-context mailing list <ntg-context@ntg.nl>
Cc: Henning Hraban Ramm <texml@fiee.net>
Subject: natural table oddities
Date: Sat, 1 Apr 2023 21:05:12 +0200	[thread overview]
Message-ID: <41faf38f-bf94-8c4f-77a3-290cd9a849b8@fiee.net> (raw)
In-Reply-To: <7C2A6538-F472-4A0F-850B-BDC0238DDBC1@scorecrow.com>

[This mail sat in my drafts folder for days; wanted to research more 
first, well…]

Am 28.03.23 um 02:19 schrieb Bruce Horrocks:
> If you're asking for comments with a view to making changes then...

I can’t make the changes myself, only suggest them to Hans.

>> On 27 Mar 2023, at 15:03, Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl> wrote:

>>> * If I format a column, e.g. \setupTABLE[c][-1][color=red], body and foot are formatted, but not the same column in header. I couldn’t find how to format columns in header.
> 
> If you disregard the Wiki page instructions to use \bTH...\eTH then you can format the header using:
\bTD ... \eTD

> but I'm not sure what the consequences might be, if any. You lose the default bold heading so maybe that's all /bTH.../eTH is adding?

Yes, I also found that out – either I sent an incomplete email, or I 
forgot to add my later “research”. 🤔

TH (table header, not Taco or Tomáš 😉) adds a separation between header 
and body cells, but setting up "header" affects both TD and TH within 
TABLEhead.

> It would be nice to have a way of specifying the header explicitly. My suggestion would be to have:
> - \setupTABLE[r][head][...] affect just the header
> - \setupTABLE[r][next][...] affect the new page header
> - \setupTABLE[r][first|last|body][...] affect the first, or last, or only the body rows (i.e. not the header or footer)
> - \setupTABLE[r][foot][...] affect just the footer
> 
> [r][last] (and [r][-1]) would represent the last body row (but not the footer row if one has been requested).

I agree.

>>> ## Formatting
>>> * maxwidth doesn’t seem to have an effect, neither on the whole table nor on a column.
>>> * textwidth works only for the whole table.
>>> * width gets stretched if option=stretch; i.e. I can’t fix the width of single cells or columns.
> 
> For me, \setupTABLE [c] [1] [width=3cm] fixes the width of column 1 and forces long text to wrap.

But the width of a column is not fixed if you set option=stretch, then 
*all* columns are stretched, not only the undefined.

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

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2023-04-01 19:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <37e3e6b3-7e8a-3673-8708-7cad3ef4cbb9@fiee.net>
2023-03-27 14:03 ` Henning Hraban Ramm via ntg-context
2023-03-28  0:19   ` Bruce Horrocks via ntg-context
2023-04-01 19:05     ` Henning Hraban Ramm via ntg-context [this message]
2023-03-14 16:50 Henning Hraban Ramm via ntg-context

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=41faf38f-bf94-8c4f-77a3-290cd9a849b8@fiee.net \
    --to=ntg-context@ntg.nl \
    --cc=texml@fiee.net \
    /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).