From: Willi Egger <w.egger@boede.nl>
Subject: Re: Why I needed \parbox and why does \framed not work here?
Date: Sun, 13 Mar 2005 18:34:34 +0100 [thread overview]
Message-ID: <423479AA.6060907@boede.nl> (raw)
In-Reply-To: <3b7b76619dc12ab169e359b6cf4e6e04@rna.nl>
hi Gerben,
Gerben Wierda wrote:
> Hi Willi,
>
> Thanks.
>
> If what you changed was the addition of the (2cm) stuff, I did try that
> but it did not change anything at that time.
>
> But now I notice that I need to start my rows with a \NC. I would have
> thought that a \NC would be like a \crlf or a \page and that it would
> have been implied in the \NR command. I find this counterintuitive.
>
No, the \NC means new column and in order to organize this I believe it
is natural to start with \NC and end with \NC\NR to indicate a new row
to be started.
> Anyway, Having that (2cm) stuff in the \startabulate makes all tables
> the same in column width. I used to be able to have one command \xttable
> where the result depended on what I had in the main text.
What about extend your definition with another parameter?
\newcommand{\xttable}[8]{\starttable[|p(#8)|p(#8)|p(#8)|] ...
KR
Willi
> So, yes, I can use p columns, but that means that all of my tables will
> hae to have identical column widths. That is why I wanted to use c
> columns and have that decision in the text. So I would still be
> interested in a way of doing \parbox in ConTeXt.
>
> (For non-LaTeX users \parbox{2cm}{text text text text etc} creates a
> paragraph 2 cm wide and sets the text in it. The height of the box is
> the result of that typesetting.)
>
> G
>
> On Mar 13, 2005, at 16:05, Willi Egger wrote:
>
>> Hi Gerben,
>>
>> There is no worry about the mentioned chaos. You might be lucky, that
>> your definition is giving a result at all.
>>
>> If you consult the manual or read the article in the MAPS22 on
>> tabulating, you will see, that you missed a correct setup of the
>> tabulation.
>>
>> I attach my version and it works.
>>
>> KR
>> Willi
>>
>> Gerben Wierda wrote:
>>
>>> Here is the example again, now with p columns. Never mind the
>>> non-working third example (ConTeXt wraps three elements in the third
>>> column now but not inside the \framed), but it seems that ConTeXt
>>> does not wrap the first column at all. As a result, the other two are
>>> very small.
>>> G
>>> PS. The ConTeXT manual does not have \starttable documentation, not
>>> does the wiki (how does 'p' work etc).
>>> % Try with 'p' columns
>>> \usemodule[bib] % defines \newcommand
>>> \newcommand{\operand}[1]{{\sc #1}}
>>> \newcommand{\ttvalue}[1]{{\sc #1}}
>>> \newcommand{\xttable}[7]{\starttable[|p|p|p|]\HL %
>>> #1 \NC #2 \NC #1 \operand{#3} #2 \SR\HL
>>> \ttvalue{false} \NC \ttvalue{false} \NC \ttvalue{#4} \FR %
>>> \ttvalue{false} \NC \ttvalue{true} \NC \ttvalue{#5} \MR %
>>> \ttvalue{true} \NC \ttvalue{false} \NC \ttvalue{#6} \MR %
>>> \ttvalue{true} \NC \ttvalue{true} \NC \ttvalue{#7} \LR\HL %
>>> \stoptable}
>>> \newcommand{\ttable}[5]{\xttable{a}{b}{#1}{#2}{#3}{#4}{#5}}
>>> \starttext
>>> Looks fine:\blank
>>> \midaligned{%
>>> \xttable{Statement X}{Statement Y}{$\Rightarrow$}%
>>> {unknown}{unknown}{invalid (false)}{valid (true)}
>>> }
>>> This doesn't work:\blank
>>> \midaligned{%
>>> \xttable{Some sort of longer statement}{Another sort of longer
>>> statement}%
>>> {$\Rightarrow$}%
>>> {unknown}{unknown}{invalid (false)}{valid (true)}
>>> }
>>> This doesn't work either:\blank
>>> \midaligned{%
>>> \xttable{\framed[width=2cm,frame=off]{Some sort\par of longer
>>> statement\par}}{\framed[width=2cm,frame=off]{Another sort\par of longer
>>> statement\par}}{$\Rightarrow$}%
>>> {unknown}{unknown}{invalid (false)}{valid (true)}
>>> }
>>> \stoptext
>>> _______________________________________________
>>> ntg-context mailing list
>>> ntg-context@ntg.nl
>>> http://www.ntg.nl/mailman/listinfo/ntg-context
>>
>> % Truthtables Gerben Wierda
>> % C0ntext file
>> % filename: truthtable-Wierda.tex
>> % Gerben Wierda
>> % W. Egger
>> % 13-03-2005
>>
>> \setupoutput[pdftex]
>> \setupbodyfont[ss,12pt]
>>
>> \usemodule[bib] % defines \newcommand
>> \newcommand{\operand}[1]{{\sc #1}}
>> \newcommand{\ttvalue}[1]{{\sc #1}}
>> \newcommand{\xttable}[7]{\starttable[|p(2cm)|p(5cm)|p(3cm)|]
>> \HL %
>> \NC #1 \NC #2 \NC #1 \operand{#3} #2 \NC\NR
>> \HL
>> \NC \ttvalue{false} \NC \ttvalue{false} \NC \ttvalue{#4} \NC\NR %
>> \NC \ttvalue{false} \NC \ttvalue{true} \NC \ttvalue{#5} \NC\NR %
>> \NC \ttvalue{true} \NC \ttvalue{false} \NC \ttvalue{#6} \NC \NR %
>> \NC \ttvalue{true} \NC \ttvalue{true} \NC \ttvalue{#7} \NC\NR\HL %
>> \stoptable}
>> \newcommand{\ttable}[5]{\xttable{a}{b}{#1}{#2}{#3}{#4}{#5}}
>> \starttext
>> Looks fine:\blank
>> \midaligned{%
>> \xttable{Statement X}{Statement Y}{$\Rightarrow$}%
>> {unknown}{unknown}{invalid (false)}{valid (true)}
>> }
>>
>>
>> This doesn't work:\blank
>> \midaligned{%
>> \xttable{Some sort of longer statement}{Another sort of longer
>> statement}%
>> {$\Rightarrow$}%
>> {unknown}{unknown}{invalid (false)}{valid (true)}
>> }
>>
>> % This doesn't work either:\blank
>> % \midaligned{%
>> % \xttable{\framed[width=2cm,frame=off]{Some sort of longer
>> % statement\par}}{\framed[width=2cm,frame=off]{Another sort of longer
>> % statement\par}}{$\Rightarrow$}%
>> % {unknown}{unknown}{invalid (false)}{valid (true)}
>> % }
>> \stoptext
>> _______________________________________________
>> ntg-context mailing list
>> ntg-context@ntg.nl
>> http://www.ntg.nl/mailman/listinfo/ntg-context
>
>
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2005-03-13 17:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-13 9:08 Gerben Wierda
2005-03-13 10:57 ` Willi Egger
2005-03-13 13:42 ` Gerben Wierda
2005-03-13 14:06 ` Gerben Wierda
2005-03-13 15:05 ` Willi Egger
2005-03-13 15:59 ` Gerben Wierda
2005-03-13 17:34 ` Willi Egger [this message]
2005-03-13 15:12 ` Willi Egger
2005-03-13 16:57 ` Patrick Gundlach
2005-03-13 20:47 ` mickle
2005-03-14 14:27 ` Taco Hoekwater
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=423479AA.6060907@boede.nl \
--to=w.egger@boede.nl \
--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).