From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: Flowing text around a figure
Date: Mon, 27 May 2002 22:35:23 +0200 [thread overview]
Message-ID: <5.1.0.14.1.20020527223226.03982df0@server-1> (raw)
In-Reply-To: <20020521082420.685b8a83.wmcclain@salamander.com>
At 08:24 AM 5/21/2002 -0500, you wrote:
>On Tue, 21 May 2002 08:53:23 +0200
>Hans Hagen <pragma@wxs.nl> wrote:
>
> > can you make me a minimal file that shows the problem?
>
>I've found that it has to do with the content of my text. Any paragraph
>beginning with a block does not flow properly. The best workaround I
>have found is to insert a \strut at the beginning of the text where it
>starts with a block.
right, this is a known weakness: if you start a par with a \command, you
may end up with yes/no indentation or some everypar interference (can for
instance be due to the fact that the command can start a group and
aftergroup things can be messed up), your \strut solution is ok (\indent \
noindent or \dontleavehmode is also ok), since they start the paragraph
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
next prev parent reply other threads:[~2002-05-27 20:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-20 21:49 Bill McClain
2002-05-21 6:53 ` Hans Hagen
2002-05-21 13:24 ` Bill McClain
2002-05-27 20:35 ` Hans Hagen [this message]
2002-05-21 10:06 ` Giuseppe Bilotta
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=5.1.0.14.1.20020527223226.03982df0@server-1 \
--to=pragma@wxs.nl \
--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).