From: Andreas Harder <aharder@uni-koblenz.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Float option “top” affects page break (on following pages)
Date: Thu, 24 Feb 2011 23:56:25 +0100 [thread overview]
Message-ID: <57DF9D05-B15F-4FFB-B855-44D4CDE89DE6@uni-koblenz.de> (raw)
In-Reply-To: <A1CC1003-838F-4CCB-8803-5BEE1BE70653@uni-koblenz.de>
Am 24.02.2011 um 14:15 schrieb Andreas Harder:
> Hi all,
>
> consider the following example.
>
> \starttext \showgrid
> Try to comment the \tex{placefigure} command, there will be 40 lines on the second page. If you uncomment it again there are 41 lines!
> \placefigure[top,nonumber]{}{\externalfigure[dummy]}
> \page
> \dorecurse{30}{line \recurselevel\par} \blank[medium,small]
> \dostepwiserecurse{31}{50}{1}{line \recurselevel\par}
> \stoptext
>
> It's really a problem if compiling a component file which ends up with another page breaking than the corresponding product file.
>
> I hope there will be soon a fix for that … is there already one?
I found a workaround. One can set
\setupinterlinespace[top=0]
Is this a bad idea? Are there any disadvantages? I would appreciate some explanations.
Greeting
Andreas
___________________________________________________________________________________
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 prev parent reply other threads:[~2011-02-24 22:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 13:15 Andreas Harder
2011-02-24 22:56 ` Andreas Harder [this message]
2011-02-25 13:44 ` Hans Hagen
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=57DF9D05-B15F-4FFB-B855-44D4CDE89DE6@uni-koblenz.de \
--to=aharder@uni-koblenz.de \
--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).