From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: bug in multiple layouts?
Date: Sat, 19 Oct 2013 00:24:08 +0200 [thread overview]
Message-ID: <5261B508.2090906@gmx.es> (raw)
In-Reply-To: <1A0271BE-A9B7-47A0-BD57-500D03F125FF@gmail.com>
On 10/18/2013 08:30 PM, Wolfgang Schuster wrote:
>> [...]
>> I found two issues: the first lines on the second page have the margin
>> from previous page, and from the third page text doesn’t reach the page
>> bottom.
>>
>> Am I missing something or have I found a bug?
>
> 1. reset is a keyword for \setuplayout (single argument version) and
> not a name for a predefined layout
>
> 2. You can’t define layouts for page ranges (e.g. 2-last), only page
> numbers (e.g. 2,5, or -3), names (e.g. mylayout) and keywords (e.g.
> first, last, odd and even) are possible.
Many thanks for your reply, Wolfgang.
I want to have a different top and bottom space only for the first page.
From I what I understand, here is a new sample (that doesn’t work):
\showframe
\setuppagenumbering[alternative=doublesided, location=]
\setuplayout[margin=20mm, width=fit, topspace=45mm, bottomspace=25mm,
height=fit]
\definelayout[first][topspace=110mm, bottomspace=30mm]
\starttext
\dorecurse{20}{\input knuth\par}
\stoptext
I define a the standard layout, a layout for the first page, but I don’t
know why the text doesn’t fill the full text area in pages other than
the first.
> 3. The width of a paragraph is fixed and tex doesn’t changed the
> width of the part which is moved to the next page (there are a fix tricks to
> work around this limitation but they work only when you have a text
> only document).
>
> 4. TeX has its limitations and you have to live with them, with
> LuaTeX there are ways to get rid of a few of them but it takes time
> to write the necessary code
As a workaround: is it possible that the text flow avoids layers as if
it were floats?
What I mean is that in the following sample the text flow avoids the
rectangle:
\definelayer[avoidasfloat][x=0mm, y=0mm, hoffset=8mm, voffset=101mm,
location={right,bottom}, state=start]
\setlayer[avoidasfloat]{\startMPcode
draw (0mm,0mm)--(55mm,0mm) ;
draw (0mm,0mm)--(0mm,-86mm) ;
draw (0mm,-86mm)--(55mm,-86mm) ;
draw (55mm,-86mm)--(55mm,0mm) ;
\stopMPcode
}
\setupbackgrounds[page][background={avoidasfloat}]
\starttext
\dorecurse{4}{\input knuth\par}
\stoptext
How could this be done?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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:[~2013-10-18 22:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 15:37 Pablo Rodriguez
2013-10-18 18:30 ` Wolfgang Schuster
2013-10-18 22:24 ` Pablo Rodriguez [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=5261B508.2090906@gmx.es \
--to=oinos@gmx.es \
--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).