From: "peter.hopcroft--- via ntg-context" <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: peter.hopcroft@icloud.com, Pablo Rodriguez <oinos@gmx.es>
Subject: Re: Seems to be a bug with \definelayout
Date: Sun, 11 Dec 2022 09:16:52 +1300 [thread overview]
Message-ID: <D47E17D7-5DEE-4DB5-8087-1F9044EA8034@icloud.com> (raw)
In-Reply-To: <22ff4c4f-64e7-b805-cdce-f306b95c2d9c@gmx.es>
Yes Pablo, that does fix it. I'm sorry, I misunderstood your first reply. Peter
> On 10/12/2022, at 10:44 PM, Pablo Rodriguez via ntg-context <ntg-context@ntg.nl> wrote:
>
> On 12/9/22 21:23, peter.hopcroft--- via ntg-context wrote:
>> I’ve rewritten my last email. The context below produces the pdf in
>> the screenshot below.
>>
>> I expect the layout[short] to be applied to pages 2 and 3. It is. But
>> there seem to be 2 bugs:
>>
>> 1 - Pages 4, 5 and 6 have the [short] layout. They should have the
>> default layout.
>>
>> 2 - On pages 5 and 6, the text flows beyond the bottom of the frame.
>> It should stop at the bottom of the frame.
>
> Hi Peter,
>
> as in my reply from yesterday, this seems to fix your bugs:
>
> \showframe
> \setuppapersize[A4][A3,landscape] \setuparranging[2SIDE]
> \setuplayout[backspace=80mm, width=100mm, topspace=50mm, header=0mm,
> footer=0mm, height=200mm, margindistance=10mm, leftmargin=40mm]
>
> \definelayout[short][backspace=80mm, width=100mm, topspace=50mm,
> header=0mm, footer=0mm, height=80mm, margindistance=10mm,
> leftmargin=40mm]
>
> \starttext
> \definelayout[even][reset]
> \definelayout[odd][reset]
> \definelayout[2][short]
> \definelayout[3][short]
> \dorecurse{10}{\input{knuth} }
> \stoptext
>
> It seems that you need to reset the layout in all other pages (where the
> special layout isn’t applied).
>
> I hope it helps,
>
> Pablo
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : https://www.pragma-ade.nl / http://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
> ___________________________________________________________________________________
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2022-12-10 20:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 20:23 peter.hopcroft--- via ntg-context
2022-12-10 9:44 ` Pablo Rodriguez via ntg-context
2022-12-10 20:16 ` peter.hopcroft--- via ntg-context [this message]
2022-12-10 20:38 ` Mikael Sundqvist via ntg-context
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=D47E17D7-5DEE-4DB5-8087-1F9044EA8034@icloud.com \
--to=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
--cc=peter.hopcroft@icloud.com \
/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).