From: Vit Zyka <vit.zyka@seznam.cz>
Subject: Re: How this LaTeX code could be translated into ConTeXt?
Date: Sat, 03 Sep 2005 15:30:05 +0200 [thread overview]
Message-ID: <4319A55D.2080900@seznam.cz> (raw)
In-Reply-To: <6faad9f005090303586ec4cbba@mail.gmail.com>
Mojca Miklavec wrote:
> Taco Hoekwater wrote:
>
>>Jilani Khaldi wrote:
>>
>>>I just want to know how to have a table in Context with cells which can
>>>contain many lines each; something like this:
>>
>> \starttabulate[|p(4cm)|p(2cm)|p(2cm)|]
>> \NC Header1 \NC header2 \NC header 3 \NC\NR
>> \NC This is a text splitted in 3 lines because it is very long
>> \NC 2005 \NC Thank you for the tip!\NC\NR
>> \stoptabulate
>
>
> Or (in the spirit of Taco's example):
>
> \bTABLE
> \setupTABLE[c][1][width=4cm]
> \setupTABLE[c][2,3][width=2cm] % 2nd and 3rd column
> \bTR
> \bTD Header1 \eTD
> \bTD header2 \eTD
> \bTD header3 \eTD
> \eTR
> \bTD This is a text splitted in 3 lines because it is very long \eTD
> \bTD 2005 \eTD
> \bTD Thank you for the tip! \eTD
> \eTABLE
>
> If text in a cell is very long, it will be splitted in more lines
> automatically, so that the table of width \textwidth will be produced.
> \bTABLE ... \eTABLE is already very clever, however, I don't know if
> you can do something similar as in the LaTeX example you provided, so
> that the overall table width is fixed to exactly 16 cm (also for a
\bTABLE[option=stretch,textwidth=16cm]
...
\eTABLE
vit
> very small table, which should artificially be expanded) without
> having to provide the width of every single column.
>
> See enattab.pdf for more details about natural tables.
>
> Mojca
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>
--
=======================================================
Ing. Vít Zýka, Ph.D. TYPOkvítek
database publishing databazove publikovani
data maintaining and typesetting in typographic quality
priprava dat a jejich sazba v typograficke kvalite
tel.: (+420) 777 198 189 www: http://typokvitek.com
=======================================================
next prev parent reply other threads:[~2005-09-03 13:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-02 13:15 Jilani Khaldi
2005-09-02 13:34 ` luigi.scarso
2005-09-02 17:28 ` Jilani Khaldi
2005-09-02 17:44 ` update modules.pdf to latest release luigi.scarso
2005-09-02 19:00 ` How this LaTeX code could be translated into ConTeXt? Taco Hoekwater
2005-09-02 22:39 ` Jilani Khaldi
2005-09-03 7:11 ` Taco Hoekwater
2005-09-03 10:58 ` Mojca Miklavec
2005-09-03 11:01 ` Mojca Miklavec
2005-09-03 12:31 ` Jilani Khaldi
2005-09-03 13:30 ` Vit Zyka [this message]
2005-09-04 22:00 ` different border thicknesses in natural tables Mojca Miklavec
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=4319A55D.2080900@seznam.cz \
--to=vit.zyka@seznam.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).