From: Hans Hagen <j.hagen@xs4all.nl>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>,
"Procházka Lukáš Ing." <LPr@pontex.cz>
Subject: Re: Mapping TABLE to xtable (module "ntb-to-xtb") doesn't recognize "c" option for columns
Date: Wed, 20 Feb 2019 09:15:40 +0100 [thread overview]
Message-ID: <d032a1c2-9278-f6b6-8d71-b5c1996ff3a5@xs4all.nl> (raw)
In-Reply-To: <op.zxh3g1fz3h68c7@lpr>
On 2/20/2019 9:06 AM, Procházka Lukáš Ing. wrote:
> Hello,
>
> On Tue, 19 Feb 2019 21:35:41 +0100, Wolfgang Schuster
> <wolfgang.schuster.lists@gmail.com> wrote:
>
>>
>>
>> Procházka Lukáš Ing. schrieb am 19.02.19 um 21:27:
>>> Hello,
>>>
>>> it seems that xtable setup doesn't recognize the "c" option, which is
>>> recognized successfully by TABLE setup;
>>> tested on mapping provided by "ntb-to-xtb" module:
>>>
>>> ----
>>> \usemodule[ntb-to-xtb] \restoreTABLEfromxtable
>>>
>>> \starttext
>>> \bTABLE
>>> \setupTABLE[c][1][width=1in] % Set 1st column width - OK with TABLE
>>> \bTR
>>> \bTD A
>>> \eTD
>>> \eTR
>>> \eTABLE
>>>
>>> \bgroup
>>> \mapTABLEtoxtable
>>> \bTABLE
>>> \setupTABLE[c][1][width=1in] % <- This line causes error - not
>>> recognized by xtable setup
>>
>> xtables don’t support row/column settings like natural table and the
>> mapping doesn’t change this.
>>
>> Wolfgang
>
> as column setup for TABLEs by "\setupTABLE[c][1][width=1in]" is handy
> and is used frequently, would it be possible to provide identical
> mechanism for xtables?
all is popssible but it won't happen ... different approach ... you can
use named setups here
> From what I read in the manual, setting width of a column for xtable is
> provided by \startxcell[width=...] at the place of the first
> cell-in-that-column usage.
>
> Moreover, when xtable is built in two passes, in the first pass it might
> take a column (width) specification(s), if provided, and keep on reading
> xcell specification(s), considering xcell width, if provided.
it already does ... even more than two passes
> I guess to be handy to implement both \setupTABLE[c][...] and
> \setupxtable[c][...] in a similar way, especially when there is a simple
> mechanism which allows TABLE/xtable switching (ntb-to-xtb module).
it would also be pretty inefficient
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2019-02-20 8:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 20:27 Procházka Lukáš Ing.
2019-02-19 20:35 ` Wolfgang Schuster
2019-02-20 8:06 ` Procházka Lukáš Ing.
2019-02-20 8:15 ` Hans Hagen [this message]
2019-02-20 9:51 ` Procházka Lukáš Ing.
2019-02-20 10:10 ` Hans Hagen
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=d032a1c2-9278-f6b6-8d71-b5c1996ff3a5@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=LPr@pontex.cz \
--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).