From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Justifying last line of paragraph
Date: Mon, 27 Sep 2010 09:18:45 +0200 [thread overview]
Message-ID: <4CA04555.4000906@elvenkind.com> (raw)
In-Reply-To: <871v8gbij5.fsf@denkblock.local>
On 09/26/2010 06:01 PM, Elias Oltmanns wrote:
> Taco Hoekwater<taco@elvenkind.com> wrote:
>> On 09/25/2010 08:03 PM, Elias Oltmanns wrote:
>>>
>>
>>> The first couple of lines of the paragraph beginning on page two should
>>> really go on the previous page. Since the hang mechanism of \placefigure
>>> doesn't work due to the page break, I'd like to split this paragraph
>>> into two logical entities, so TeX can put the first on the first page
>>> and treat the second as a separate paragraph flowing around the picture.
>>> However, the reader should not be aware of this split.
>>>
>>> Any help much appreciated,
>>
>> I don't know of any automatic solution to this problem (except _perhaps_
>> columnsets could help) but the simplest way to split a paragraph into
>> two paragraphs while still looking like one is by inserting a macro
>> like this at an existing break point:
>
> Thanks Taco, this appears to be exactly what I was looking for. One more
> thing though: is there a simple way to arrange for all arguments
> provided to \splitpar to be passed on to \placefigure in a definition
> like this:
Something like this should work:
\def\splitpar#1%
{\bgroup
....
\gdef\splitparcommands{\placefigure#1\parskip...}%
\aftergroup \splitparcommands
\egroup}
The definition is all about \aftergroup: each \aftergroup adds exactly
one *token* to the list of things to run after the group ends. Passing
arguments that way is tedious and very error prone (you would need
something like \adtergroup [ \aftergroup l \aftergroup e \aftergroup f
... ), so defining a global macro and passing that is better.
I did not do this in the earlier version because if you can get around
using \gdef, it is usually wise to do so. Sorry, I have no idea whether
it is possible to do this stuff with a nicer, more ConTeXt interface.
Best wishes,
Taco
___________________________________________________________________________________
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:[~2010-09-27 7:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-25 18:03 Elias Oltmanns
2010-09-26 7:55 ` Taco Hoekwater
2010-09-26 16:01 ` Elias Oltmanns
2010-09-27 7:18 ` Taco Hoekwater [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=4CA04555.4000906@elvenkind.com \
--to=taco@elvenkind.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).