From: Alan BRASLAU <alan.braslau@cea.fr>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <pragma@wxs.nl>
Subject: Re: Misbehaving \starthanging\stophanging
Date: Mon, 21 Jan 2013 20:09:44 +0100 [thread overview]
Message-ID: <20130121200944.275e15f6@iram-hb-003386.extra.cea.fr> (raw)
In-Reply-To: <50FD8D69.5010100@wxs.nl>
On Mon, 21 Jan 2013 19:48:09 +0100
Hans Hagen <pragma@wxs.nl> wrote:
> On 1/19/2013 12:06 PM, Alan BRASLAU wrote:
> > Hello,
> >
> > \starthanging\stophanging is a very appreciated feature.
> >
> > However, hanging text wrapped around a figure fails if a new
> > paragraph intervenes.
> >
> > Minimal example:
> >
> > \starttext
> > \starthanging [location=right] {\externalfigure [cow]
> > [width=.3\textwidth]} This is a first paragraph.
> >
> > \input tufte
> > \stophanging
> > \stoptext
>
> currently somewhat limited as it's not like the regular place left
> figure macro using the otr .. so the hang is forgotten after a par
> which means that you need to use \break or \crlf or something nor
> \par:
>
> \starttext
> \starthanging [location=right] {\externalfigure [cow]
> [width=.3\textwidth]} This is a first paragraph.\crlf \input tufte
> \stophanging
> \stoptext
>
>
> (some day i'll make a nice one)
Of course, I can use \crlf or \break.
By the way, I have encountered situations where the regular place
figure macro misbehaves as well.
Mimimal example:
\starttext
\startplacefigure [location=right,number=no]
\externalfigure [cow] [width=.3\textwidth]
\stopplacefigure
This is a first paragraph.
\startquotation
\input tufte
\stopquotation
\stoptext
Alan
___________________________________________________________________________________
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-01-21 19:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 11:00 Misbehaving flow charts Marco Patzer
2013-01-17 12:12 ` Marco Patzer
2013-01-19 9:20 ` Hans Hagen
2013-01-19 10:52 ` Marco Patzer
2013-01-19 11:28 ` Wolfgang Schuster
2013-01-19 13:11 ` Hans Hagen
2013-01-19 11:06 ` Misbehaving \starthanging\stophanging Alan BRASLAU
2013-01-21 18:48 ` Hans Hagen
2013-01-21 19:09 ` Alan BRASLAU [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=20130121200944.275e15f6@iram-hb-003386.extra.cea.fr \
--to=alan.braslau@cea.fr \
--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).