From: Steffen Wolfrum <context@st.estfiles.de>
Cc: pragma@wxs.nl
Subject: Re: columnset BUG - (urgent!)
Date: Sun, 28 Nov 2004 22:32:47 +0100 [thread overview]
Message-ID: <a06002002bdcff34b929b@[62.134.78.0]> (raw)
thanks, that works now.
but do you also know the answer to the second bug:
When you uncomment the lines (testfile below)
the columnset gets 2 lines shorter!
I experienced this when I added before the literature component
a catalogue component that uses a structure like the commented lines do.
So I had two separate files actually!
Steffen
\starttext
\showframe
\showgrid
% oiuoiuoiuoiuoi \footnote{aaaa}
% \startcolumns[balance=yes,rule=off,n=2,distance=1cm]
% text \par
% text
% \stopcolumns
% gfdgfdgfdgfdgfdgfd \footnote{bbb}
% \page
\definecolumnset[litera][n=2,distance=1cm]
\startcolumnset[litera]
\dorecurse{10}{test \input zapf \input ward}
\stopcolumnset
\stoptext
h h extern <pragma@wxs.nl> wrote:
> Steffen Wolfrum wrote:
> > Hi,
> >
> > please have a look at testfile below:
> > without a footnote everything works fine,
> > but with the footnote the columnset gets crashed!
>
> this is a tricky situation:
>
> - the note is built in one column mode
> - but flushed in column mode (dus to postponing)
> - so actually what you see is a mixture
>
> you may try:
>
> \starttext
>
> \chapter{Heading\notesymbol[x]}
>
> \definecolumnset[litera][n=2,distance=1cm]
>
> \startcolumnset[litera]
>
> \footnotetext[x]{xx}\dorecurse{10}{test \input zapf \input ward}
>
> \stopcolumnset
> \stoptext
>
> or
>
> \starttext
>
> \definecolumnset[litera][n=2,distance=1cm]
> \definecolumnsetspan[litera][n=2]
>
> \startcolumnset[litera]
>
> \startcolumnsetspan[litera]
> \chapter{Heading\notesymbol[x]}
> \stopcolumnsetspan
>
> \footnotetext[x]{xx}\dorecurse{10}{test \input zapf \input ward}
>
> \stopcolumnset
> \stoptext
>
>
>
> > I noticed this bug in a bigger book project:
> > The columnset is at the end as a seperate document (\component).
> > And the footnote was added 300 pages and 5 component files before !!!
> >
> > As this footnote was one of the last changes that were done
> > before I wanted to send the book to the printer
> > a fast help would be very much appreciated.
> >
> > Sorry, but it's really quite urgent -
> >
> > Steffen
> >
> > %&context
> > \starttext
> > \chapter{Heading\footnote{x}}
> >
> > \definecolumnset[litera][n=2,distance=1cm]
> >
> > \startcolumnset[litera]
> >
> > \dorecurse{10}{test \input zapf \input ward}
> >
> >
> > \stopcolumnset
> > \stoptext
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
> | www.pragma-pod.nl
> -----------------------------------------------------------------
>
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
next reply other threads:[~2004-11-28 21:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-28 21:32 Steffen Wolfrum [this message]
2004-11-29 11:13 ` Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2004-11-25 23:11 Steffen Wolfrum
2004-11-27 20:11 ` h h extern
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='a06002002bdcff34b929b@[62.134.78.0]' \
--to=context@st.estfiles.de \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).