* tables for invoice-style
@ 2003-02-07 7:02 Roef Ragas
2003-02-07 9:48 ` Hans Hagen
0 siblings, 1 reply; 4+ messages in thread
From: Roef Ragas @ 2003-02-07 7:02 UTC (permalink / raw)
Goodevening all,
The examples in the 'natural tables' manual are nice [although I keep
wondering why you would {\em ever} need some specimina], but what I'm
looking I'm not able to fabricate.
What I want is one line with words like invoice: date: etcetera,
and the following line will contain the proper data [like in Victor
Eijkhouts ntg-letter].
I'm not sure tables (maybe columns?) are the solution, but this is what
I've got [a portion of it] sofar. It won't work, that is: somehow I'm
not able to adjust the width of the columns? Can anybody see what's
wrong here?
\starttekst
\hbox \bgroup \ignorespaces
\bTABLE
\setupTABLE[column][1][width=1cm]
\setupTABLE[column][2][width=2cm]
\setupTABLE[column][3][width=3cm]
\setupTABLE[column][4][width=4cm]
\setupTABLE[column][5][width=10cm]
\bTR
\bTD {\ss\bf factuur:} \eTD
\bTD {\ss\bf debiteur:} \eTD
\bTD {\ss\bf betreft:} \eTD
\bTD {\ss\bf de dato:} \eTD
\bTD {\ss\bf uw kenmerk:} \eTD
\eTR
\bTR
\bTD \getvariable{factuur}{factuurnummer} \eTD
\bTD \getvariable{factuur}{debiteurnummer} \eTD
\bTD \getvariable{factuur}{betreft}\eTD
\bTD \getvariable{factuur}{werkdatum}\eTD
\bTD \getvariable{factuur}{uwkenmerk}\eTD
\eTR
\eTABLE
\unskip \egroup
\stoptekst
Furthermore this section of the Invoice-style will be followed by
figures ;-], and again my question is: should I use columns or tables
here?
Thanks in advance,
Roef Ragas
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: tables for invoice-style
2003-02-07 7:02 tables for invoice-style Roef Ragas
@ 2003-02-07 9:48 ` Hans Hagen
2003-02-07 10:58 ` Adam Lindsay
0 siblings, 1 reply; 4+ messages in thread
From: Hans Hagen @ 2003-02-07 9:48 UTC (permalink / raw)
At 08:02 AM 2/7/2003 +0100, you wrote:
>Goodevening all,
>
>The examples in the 'natural tables' manual are nice [although I keep
>wondering why you would {\em ever} need some specimina], but what I'm
>looking I'm not able to fabricate.
>
>What I want is one line with words like invoice: date: etcetera,
>and the following line will contain the proper data [like in Victor
>Eijkhouts ntg-letter].
>
>I'm not sure tables (maybe columns?) are the solution, but this is what
>I've got [a portion of it] sofar. It won't work, that is: somehow I'm
>not able to adjust the width of the columns? Can anybody see what's
>wrong here?
>
>
>\starttekst
>\hbox \bgroup \ignorespaces
>\bTABLE
>\setupTABLE[column][1][width=1cm]
>\setupTABLE[column][2][width=2cm]
>\setupTABLE[column][3][width=3cm]
>\setupTABLE[column][4][width=4cm]
>\setupTABLE[column][5][width=10cm]
>\bTR
>\bTD {\ss\bf factuur:} \eTD
>\bTD {\ss\bf debiteur:} \eTD
>\bTD {\ss\bf betreft:} \eTD
>\bTD {\ss\bf de dato:} \eTD
>\bTD {\ss\bf uw kenmerk:} \eTD
>\eTR
>\bTR
>\bTD \getvariable{factuur}{factuurnummer} \eTD
>\bTD \getvariable{factuur}{debiteurnummer} \eTD
>\bTD \getvariable{factuur}{betreft}\eTD
>\bTD \getvariable{factuur}{werkdatum}\eTD
>\bTD \getvariable{factuur}{uwkenmerk}\eTD
>\eTR
>\eTABLE
>\unskip \egroup
>\stoptekst
hm, here it works although your first column is quite narrow
you use english keywords in a dutch context, so change column into kolom
and width into breedte
how about:
\setupTABLE[row] [1] [style=\ss\bf] % letter=
which makes the first row cleaner:
\bTR
\bTD factuur: \eTD
\bTD debiteur: \eTD
\bTD betreft: \eTD
\bTD de dato: \eTD
\bTD uw kenmerk: \eTD
\eTR
no grouping needed, sinze the cell is basically a \framed
nevertheless, i would opt for:
\starttabulate[||i1|i1|i1|i1|] % \starttabulatie
\NC \ss \bf factuur:
\NC \ss \bf debiteur:
\NC \ss \bf betreft:
\NC \ss \bf de dato:
\NC \ss \bf kenmerk: \NC\NR
\NC test
\NC another test
\NC and another one
\NC and one more
\NC done \NC \NR
\stoptabulate % \stoptabulatie
(btw, some next release will have an example interface to letters and an
associated database)
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: tables for invoice-style
2003-02-07 9:48 ` Hans Hagen
@ 2003-02-07 10:58 ` Adam Lindsay
2003-02-07 12:04 ` Hans Hagen
0 siblings, 1 reply; 4+ messages in thread
From: Adam Lindsay @ 2003-02-07 10:58 UTC (permalink / raw)
Hans Hagen said this at Fri, 7 Feb 2003 10:48:12 +0100:
>>\bTABLE
>>\eTABLE
>
>nevertheless, i would opt for:
>
>\starttabulate[||i1|i1|i1|i1|] % \starttabulatie
>\stoptabulate % \stoptabulatie
Hmm, that's something else I haven't quite understood--the pros and cons
of the three TABLE mechanisms. I've only bothered to learn \bTABLE,
because it's closest to the HTML tables I already knew well, and because
it was advertised as being the most powerful.
Could someone who knows more than I do give a brief summary of why I
would want either of the two other table mechanisms over the newest TABLE?
>(btw, some next release will have an example interface to letters and an
>associated database)
Hans, is this the same release that will include the "splitting tables
over multiple pages" feature you've mentioned?
Cheers,
adam
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Adam T. Lindsay atl@comp.lancs.ac.uk
Computing Dept, Lancaster University +44(0)1524/594.537
Lancaster, LA1 4YR, UK Fax:+44(0)1524/593.608
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: tables for invoice-style
2003-02-07 10:58 ` Adam Lindsay
@ 2003-02-07 12:04 ` Hans Hagen
0 siblings, 0 replies; 4+ messages in thread
From: Hans Hagen @ 2003-02-07 12:04 UTC (permalink / raw)
At 10:58 AM 2/7/2003 +0000, Adam Lindsay wrote:
>Hmm, that's something else I haven't quite understood--the pros and cons
>of the three TABLE mechanisms. I've only bothered to learn \bTABLE,
>because it's closest to the HTML tables I already knew well, and because
>it was advertised as being the most powerful.
>
>Could someone who knows more than I do give a brief summary of why I
>would want either of the two other table mechanisms over the newest TABLE?
\starttable : fast, some limitations (less spanning), based on patched TaBlE
\starttabulate : reasonable fast, no vertical lines, auto-width par's,
split across pages
\bTABLE : flexible, automatic, slow, no templates
so, for paragraph based tables i use tabulate, for fancy stuff i use
bTABLE, otherwise i use table
> >(btw, some next release will have an example interface to letters and an
> >associated database)
>
>Hans, is this the same release that will include the "splitting tables
>over multiple pages" feature you've mentioned?
ah, that's mechanism number 4; already in there but undocumented -)
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2003-02-07 12:04 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-02-07 7:02 tables for invoice-style Roef Ragas
2003-02-07 9:48 ` Hans Hagen
2003-02-07 10:58 ` Adam Lindsay
2003-02-07 12:04 ` Hans Hagen
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).