From: "Stefan Müller" <warrence.stm@gmx.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <pragma@wxs.nl>
Subject: Re: margin notes at page breaks
Date: Sun, 13 Nov 2011 12:12:07 +0100 [thread overview]
Message-ID: <4EBFA607.80901@gmx.de> (raw)
In-Reply-To: <4EB17117.8070308@wxs.nl>
Hi Hans,
sorry to bother you again with this. I just had a look again on this
issue with 20111112 12:34 MkIV. In the first part of your example, I
see the three stacked footnotes and the first lines of the paragraph
moved to the next page. In your second example I get the three notes
stacked on the first page, one being in the bottom margin, and the
paragraph properly wrapped, with two lines on the first page. This
seems to be correct.
Unfortunately I don't understand how this should help me with my (now
updated) previous example:
\starttext
\dorecurse{4}{\input knuth} \blank[2*line]
\inmargin[stack=yes]{This note ends up in the bottom margin}
\input tufte
\stoptext
It still looks the same. Does the stacking only influence the behaviour
of (the breaking between) multiple margin notes?
Thank you for looking into this. Best regards,
Stefan
On 02.11.2011 17:34, Hans Hagen wrote:
> On 31-10-2011 13:57, Stefan Müller wrote:
>> Hi list!
>>
>> In my document I have some margin notes that appear right before a page
>> break and so end up in the bottom margin, see the following example.
>>
>> \starttext
>> \dorecurse{4}{\input knuth}
>> \blank[2*line]
>>
>> \inmargin{This note ends up in the bottom margin}
>> %\margintext{This note ends up in the bottom margin}
>> \input tufte
>> \stoptext
>>
>> Is it possible to automatically move the margin note in those cases to
>> the next page? I had a look at the manual where the issue is addressed.
>> As I understood it "\margintext{...}" should be able to handle this, but
>> it did not change anything in my example. In the garden I found
>> "\setupinmargin[stack=yes]" but this didn't help either.
>>
>> This seems not to hard, but I can't find a way to fix it...
>
> it's not supported in the current code but the next beta will have :
>
> starttext
>
> \dorecurse{4}{\input knuth} \blank[2*line]
>
> \dorecurse{3}{\inmargin[stack=yes]{note}} \input tufte
>
> \page
>
> \dorecurse{4}{\input knuth} \blank[2*line]
>
> \dorecurse{3}{\inmargin[stack=yes,bottomspace=10cm]{note}} \input tufte
>
> \stoptext
>
> with bottomspace one can set the threshold
>
> Hans
___________________________________________________________________________________
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-11-13 11:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 12:57 Stefan Müller
2011-11-02 16:34 ` Hans Hagen
2011-11-13 11:12 ` Stefan Müller [this message]
2011-11-14 8:32 ` Hans Hagen
2011-11-14 11:44 ` Stefan Müller
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=4EBFA607.80901@gmx.de \
--to=warrence.stm@gmx.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).