From: Gordon Parrott <gordon.parrott@btconnect.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: problem with columnsetspan
Date: Fri, 22 Jul 2011 11:34:42 +0100 [thread overview]
Message-ID: <AB9DA870-CB2D-4A56-87CA-6D1E4C115F89@btconnect.com> (raw)
Hi All,
I wonder if you can help:
I have been having a problem with \startcolumnsetspan when I was trying to create a magazine layout for a Uk psychodrama organisation.
Out of curiosity ( and in the hope i might learn something) i turned on tracing for a short example that gives the problem
here is the source of the test.
\setuppapersize[A4][A4]
\definecolumnset[columntest][n=3]%
\definecolumnsetspan[wide][n=2]%
\starttext
\startcolumnset[columntest]
\input knuth
\tracingall
\startcolumnsetspan[wide]
\dorecurse{3}{\input knuth\par}
\stopcolumnsetspan
\dorecurse{10}{\input knuth\par}
\stopcolumnset
\stoptext
of course it spewed out a huge log file but when looking at it i found this:
\dostartcolumnsetspan [#1][#2][#3]->\endgraf \vskip \zeropoint \bgroup \forgetall \ifnum \columnsetlevel >\zerocount \else \columnsetspanhsize \hsize \nofcolumns \plusone \mofcolumns \plusone \fi \setupframedtexts [cs:#1] [\c!width =\columnsetspanhsize , \c!linecorrection =\v!off , \c!depthcorrection =\v!off , #2]\!!countc \namedframedtextparameter {cs:#1}\c!n \!!countd \nofcolumns \ifnum \!!countc >\!!countd \!!countc \!!countd \fi \advance \!!countd -\mofcolumns \advance \!!countd \plusone \doif {\namedframedtextparameter {cs:#1}\c!alternative }\v!a {\ifnum \!!countc >\!!countd \!!countc \!!countd \fi }\setcolumnsetspanhsize \mofcolumns \!!countc \hsize \columnsetspanhsize \setbox \scratchbox \vbox \bgroup \dostartframedtext [cs:#1][\v!none ]\ifnum \columnsetlevel >\zerocount \namedframe
dtextparameter {cs:#1}\c!before \fi \unexpanded \def \stopcolumnsetspan {\dostopcolumnsetspan {#1}}
#1<-wide
#2<-
#3<-
{\par}
Lua linebreak_filter failed, reverting to default on line 9
Any ideas? my actual document exhibits the same sort of fault. It used to work before I had to update the minimals ( some time ago) when I moved to another computer and it failed then.
I must say I really like context and appreciate all the hard work that must have gone into it. I know that it is a large system and will take me some time to get to grips with.
Any help would be appreciated.
Cheers
Gordon
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2011-07-22 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 10:34 Gordon Parrott [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-09-20 7:13 Problem with \columnsetspan Marcin Borkowski
2011-09-20 19:27 ` Marcin Borkowski
2011-09-21 18:43 ` Marcin Borkowski
2011-09-27 13:26 ` Marcin Borkowski
2011-09-27 18:05 ` Hans Hagen
2011-09-27 20:01 ` Marcin Borkowski
2011-05-18 11:29 2 problems with \date[] Peter Münster
2011-05-21 14:10 ` problem with columnsetspan Gordon Parrott
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=AB9DA870-CB2D-4A56-87CA-6D1E4C115F89@btconnect.com \
--to=gordon.parrott@btconnect.com \
--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).