From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: empty lines messing with margins (in duplex mode)
Date: Sat, 12 Nov 2011 23:35:40 +0100 [thread overview]
Message-ID: <4EBEF4BC.3010204@wxs.nl> (raw)
In-Reply-To: <20111110145759.41037a4c@freenet.de>
On 10-11-2011 14:57, Peter Schorsch wrote:
> Hi,
>
> I am not sure but maybe it is a bug: in duplex documents empty lines
> causing a mess with the margins on every second page.
>
> Following lines create a fine pdf documents and all margins are set
> correctly in the pdf file:
>
> ....
> \ininner{X X X X X X X X X X X X}\inouter{M M M M M M M M M M M
> M }\input tufte
> \ininner{X X X X X X X X X X X X}\inouter{M M M M M M M M M M M
> M }\input tufte
> \ininner{X X X X X X X X X X X X}\inouter{M M M M M M M M M M M
> M }\input tufte
> ....
>
> But as soon I add between every two lines an empty line the margin on
> every second page are corrupted. I am using the context version
> 2011.11.08.
>
> I attached example files to reproduce and show the problem:
>
> duplex-margin-with-empty-lines.tex> problem occurs
>
> duplex-margin-without-empty-lines.tex> no problem
>
> Can anyone approve this problem? Or did I something totally stupid to
> get this result?
it's unrelated to newlines ... it's just that the analysis of stacking
works over a limited range (btw, in any case you'd have to say stack=yes
in order to get that)
i've added an extra option: continue:
\setuplayout
[margin=1cm]
\showframe
\starttext
\dorecurse {3} {
\ininner[stack=yes]{\expanded{\dorecurse{12}{IM\recurselevel\space}}}%
\inouter[stack=yes]{\expanded{\dorecurse{12}{OM\recurselevel\space}}}%
\input tufte \par
}
\page
\dorecurse {3} {
\ininner[stack=continue]{\expanded{\dorecurse{12}{IM\recurselevel\space}}}%
\inouter[stack=continue]{\expanded{\dorecurse{12}{OM\recurselevel\space}}}%
\input tufte \par
}
\stoptext
which will be in the next beta ... quite experimental and not yet tuned
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2011-11-12 22:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 13:57 Peter Schorsch
2011-11-12 22:35 ` Hans Hagen [this message]
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=4EBEF4BC.3010204@wxs.nl \
--to=pragma@wxs.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).