From: Simon Pepping <spepping@scaprea.hobby.nl>
Subject: Re: table page breaking
Date: Fri, 21 Mar 2003 22:47:17 +0100 [thread overview]
Message-ID: <20030321214717.GA3794@scaprea> (raw)
In-Reply-To: <5.1.0.14.1.20030320104338.0386ead0@server-1>
On Thu, Mar 20, 2003 at 10:44:23AM +0100, Hans Hagen wrote:
> tabulate will break
>
> table will break when asked for
>
> bTABLE will break when split=yes
>
> linetables will break horizontally and vertically
The option \setupTABLE[split=yes] causes errors in
DocbookInContext. The revision history gives an error, tables in the
body do not obey this option.
The error in the revision history is as follows:
! Missing } inserted.
<inserted text>
}
<to be read again>
\halign
\begintbl ... \rowTBL \tabskip \zeropoint \halign
\bgroup \registerparoption...
<inserted text> \begintbl
\begintblrow \makeTBL {1}{1}\nexttblcol \makeTBL {...
\endTBL ...tblbox \scratchbox \else \the \tbltoks
\fi \else \vbox {\the \tbl...
\eTABLE ...{\doTBL {\row }{\col }}}\eTBL }\endTBL
\egroup \egroup \popTBL
l.52 \eTABLE
\egroup
? x
The following file mimics what happens when the revision history is
processed, and generates the same error:
\setupTABLE[split=yes]
\starttext
\section{One}
Some text to continue with. Some text to continue with. Some text to
continue with. Some text to continue with. Some text to continue
with. Some text to continue with. Some text to continue with. Some
text to continue with. Some text to continue with. Some text to
continue with. Some text to continue with. Some text to continue
with. Some text to continue with. Some text to continue with.
\unprotect
\def\??xmldb {xmldb}
\def\??xmldbrevhist {\??xmldb rvh}
\setvalue{\??xmldbrevhist date}{Date}
\setvalue{\??xmldbrevhist authorinitials}{Author}
\setvalue{\??xmldbrevhist revnumber}{Revision}
\setvalue{\??xmldbrevhist revremark}{Remark}
\setvalue{\??xmldbrevhist revdescription}{Description}
\def\XMLDBenvironmentSaveElement#1%
{\@EA\gdef\csname XMLDBused!#1\endcsname{1}}
\def\XMLDBElementList{revnumber,date,authorinitials,revremark,revdescription}
\processcommacommand[revnumber,date,authorinitials]\XMLDBenvironmentSaveElement
\def\XMLDBshowElementTH#1{%
\@EA\ifx\csname XMLDBused!#1\endcsname\relax\else
\bTH\getvalue{\??xmldbrevhist #1}\eTH
\doglobal\addtocommalist{#1}\XMLDBElementsUsed
\fi
}
\def\XMLDBshowElementTD#1{%
\safeexpanded{\bTD \ignorespaces \csname #1:data\endcsname}\eTD}
\gdef\XMLDBElementsUsed{}%
\midaligned\bgroup
\setupTABLE[frame=off]
\setupTABLE[row][first][topframe=on]
\setupTABLE[row][first,last][bottomframe=on]
\bTABLE
% typeset header and construct the list of elements used
\bTR\processcommacommand[\XMLDBElementList]\XMLDBshowElementTH\eTR
% process content second pass
\setvalue{revnumber:data}{0.5}
\setvalue{date:data}{21 March 2003}
\setvalue{authorinitials:data}{SP}
\bTR\processcommacommand[\XMLDBElementsUsed]\XMLDBshowElementTD\eTR
\XMLflush{revhistory}%
\eTABLE\egroup
\protect
\stoptext
Regards, Simon
--
Simon Pepping
email: spepping@scaprea.hobby.nl
next prev parent reply other threads:[~2003-03-21 21:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 19:59 Michael Wiedmann
2003-03-20 9:44 ` Hans Hagen
2003-03-21 21:47 ` Simon Pepping [this message]
2003-03-22 12:17 ` Hans Hagen
2003-03-22 14:27 ` Willi Egger
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=20030321214717.GA3794@scaprea \
--to=spepping@scaprea.hobby.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).