From: Simon Pepping <spepping@scaprea.hobby.nl>
Subject: Re: Re[3]: In-paragraph display
Date: Tue, 3 Dec 2002 20:47:12 +0100 [thread overview]
Message-ID: <20021203194712.GA1003@scaprea> (raw)
In-Reply-To: <13EC3A06-065D-11D7-B956-0030657A7050@fastmail.fm>
On Mon, Dec 02, 2002 at 08:18:06PM -0500, Bruce D'Arcus wrote:
>
> On Monday, December 2, 2002, at 07:37 PM, Giuseppe Bilotta wrote:
>
> For what it's worth, I agree with Giuseppe here. It's the same issue
> I had with block quotes: that even if there's no blank line, ConTeXt
> assumes new paragraph.
I agree with Giuseppe and Bruce as well.
A paragraph with a displayed item in the middle, looks different to
the typesetter than to the reader: For the typesetter it consists of
three "display areas". For the reader it consists of a single
paragraph with a part standing out by its layout. The author registers
his intention to consider this as a single paragraph by not issuing
\par commands, not explicitly and no blank lines around the displayed
item.
AFAIK, in HTML such a paragraph is forbidden; a "block item" cannot
contain other "block items".
In LaTeX this situation is handled by the everypar mechanism. The end
of the display environment inserts into everypar a "once only"
noindent command. If the author issues a \par command after the
displayed item, explicitly or by a blank line, the noindent is
consumed by this empty paragraph. The following text will see the
normal everypar, with a normal parindent. It is a fragile mechanism,
and for a class author it is always a problem to get this right. (It
also bluntly resets everypar, thus disabling any other usage of it.) I
am not sure how a \par command before the displayed item is treated.
In context \setupdescriptions has a 'indentnext=no' option. In
DocbookInContext I have tried to use it, in variablelist and
glosslist. I did not see a result.
Regards, Simon
--
Simon Pepping
email: spepping@scaprea.hobby.nl
next prev parent reply other threads:[~2002-12-03 19:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-01 9:06 Giuseppe Bilotta
2002-12-02 14:34 ` Hans Hagen
2002-12-02 17:03 ` Re[2]: " Giuseppe Bilotta
2002-12-02 17:40 ` Hans Hagen
2002-12-03 0:37 ` Re[3]: " Giuseppe Bilotta
2002-12-03 1:18 ` Bruce D'Arcus
2002-12-03 9:25 ` Re[5]: " Giuseppe Bilotta
2002-12-03 10:46 ` Hans Hagen
2002-12-03 11:12 ` Re[6]: " Giuseppe Bilotta
2002-12-03 12:48 ` Hans Hagen
2002-12-03 15:24 ` Re[7]: " Giuseppe Bilotta
2002-12-03 19:47 ` Simon Pepping [this message]
2002-12-03 11:00 ` Re[3]: " Hans Hagen
2002-12-03 15:24 ` Re[4]: " 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=20021203194712.GA1003@scaprea \
--to=spepping@scaprea.hobby.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).