From: Rik Kabel <context@rik.users.panix.com>
To: ntg-context@ntg.nl
Subject: Re: Problem with margin figures and whitespace in text
Date: Sun, 26 Apr 2015 15:49:00 -0400 [thread overview]
Message-ID: <553D412C.9010007@rik.users.panix.com> (raw)
In-Reply-To: <553D27DC.9050208@wxs.nl>
On 2015-04-26 14:01, Hans Hagen wrote:
> On 4/26/2015 3:32 AM, Rik Kabel wrote:
>> I have two problems with figures placed into the left or right margin.
>> When the figure is in a group, extra whitespace is inserted between the
>> paragraphs that precede and follow the placefigure command. This happens
>> for figures placed by startplacefigure/stopplacefigure and tradiitonal
>> placefigure commands, and paragraphs placed by
>> startparagraph/stopparagraph or marked by par or newlines.
>>
>> When the figure is not in a group, whitespace called for by
>> \setupwhitespace is lost, except when the paragraphs are marked by
>> traditional means. That is, whitespace is lost when
>> startparagraph/stopparagraph is used.
>>
>> Interestingly, when that is changed to bpar/epar, the problem for
>> ungrouped figures disappears, but as I understand it, bpar/epar is not a
>> real substitute for startparagraph/stopparagraph.
>>
>> There is probably a simple explanation, but it eludes me. I prefer to be
>> able to use startparagraph/stopparagraph, and it is sometimes desirable
>> to place a figure into a group in order to prevent unique settings from
>> leaking out.
>
> you can test with this in cont-new.mkiv
>
> \unprotect
>
> \def\page_sides_inject_dummy_lines
> {\begingroup
> \scratchcounter\pageshrink
> \divide\scratchcounter \baselineskip
> \advance\scratchcounter \plusone
> \parskip\zeropoint
> \dorecurse\scratchcounter{\hbox to \hsize{}}%
> \kern-\scratchcounter\baselineskip
> \penalty\zerocount
> \endgroup}
>
> \def\page_sides_prepare_space
> {\par
> %\whitespace
> \begingroup
> \forgetall
> \reseteverypar
> \verticalstrut
> \vskip-\struttotal
> \endgroup}
>
> \protect
>
Thank you, Hans. That works well, both on the example and on a more
complex real document.
--
Rik
___________________________________________________________________________________
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:[~2015-04-26 19:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-26 1:32 Rik Kabel
2015-04-26 18:01 ` Hans Hagen
2015-04-26 19:49 ` Rik Kabel [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=553D412C.9010007@rik.users.panix.com \
--to=context@rik.users.panix.com \
--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).