From: Giuseppe Bilotta <gip.bilotta@iol.it>
Subject: Re[2]: Displayed material, again
Date: Tue, 11 Mar 2003 11:08:17 +0100 [thread overview]
Message-ID: <793170919.20030311110817@iol.it> (raw)
In-Reply-To: <5.1.0.14.1.20030311001735.0303a7e8@server-1>
Tuesday, March 11, 2003 Hans Hagen wrote:
HH> btw, here are shorter defs:
HH> \def\startdisplay
HH> {\relax\ifvmode\else\endgraf\noindent\fi\ignorespaces}
HH> \def\stopdisplay
HH> {\par\doifnextcharelse\par\donothing\noindent}
HH> watch the \relax (prevents lookahead) and \doifnextcharelse
Good to know, thanks. BTW, have you had a look at the patches I
submitted to the list around 10pm yesterday? What do you think of
them?
HH> anyway,
HH> isn't a \stopdisplay followed by an empty line still supposed to be a
HH> display?
Yes it is, and it conceptually belongs to the previous paragraph,
but the following text is not part of the same paragraph and
should therefore start with indentation.
HH> , so the full model is:
HH> \startparagraph
HH> text or not
HH> \startdisplay
HH> \stopdisplay
HH> text or not
HH> \stopparagraph
HH> the startparagraph and stopparagraph can be kind of automatic, but that's
HH> just an added bonus for those who want to use empty lines as signals
HH> (something which is not common, for instance in xml where proper tagging
HH> takes place).
Anything that gives a "paragraph end" should work. This is why in
the patches I submitted I made a small change: it suffices to give
a \noindent, regardless of what comes after, so that:
(1) if paragraph doesn't end (by any mean: no \par, no empty line,
no </para>), the next text will typographically belong to the same
paragraph (i.e. will not be indented)
(2) if paragraph ends (by any mean: \par, empty line, </para>),
the next text will be indented, since the paragraph end will
"absorb" the \noindent.
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2003-03-11 10:08 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 16:25 Giuseppe Bilotta
2003-03-10 16:50 ` Bruce D'Arcus
2003-03-10 20:22 ` Re[2]: " Giuseppe Bilotta
2003-03-10 22:15 ` s-mag-01 Bruce D'Arcus
2003-03-11 8:00 ` s-mag-01 Hans Hagen
2003-03-11 14:11 ` s-mag-01 Bruce D'Arcus
2003-03-11 14:31 ` s-mag-01 Hans Hagen
2003-03-11 14:34 ` s-mag-01 Bruce D'Arcus
2003-03-11 14:46 ` Fonts again in ConTeXt Patrick Gundlach
2003-03-11 15:10 ` Bruce D'Arcus
2003-03-12 13:04 ` Maarten Sneep
2003-03-12 13:23 ` Bruce D'Arcus
2003-03-12 13:26 ` Maarten Sneep
2003-03-12 14:05 ` Patrick Gundlach
2003-03-12 15:11 ` Hans Hagen
2003-03-12 15:43 ` Patrick Gundlach
2003-03-12 19:35 ` Jens-Uwe Morawski
2003-03-13 8:31 ` Patrick Gundlach
2003-03-14 8:27 ` Hans Hagen
2003-03-12 20:26 ` Hans Hagen
2003-03-13 8:54 ` Patrick Gundlach
2003-03-13 12:37 ` Hans Hagen
2003-03-13 15:07 ` John Culleton
2003-03-13 15:52 ` Hans Hagen
2003-03-21 18:05 ` Patrick Gundlach
2003-03-22 11:10 ` Hans Hagen
2003-03-14 21:34 ` Henning Hraban Ramm
2003-03-14 21:24 ` Henning Hraban Ramm
2003-03-21 18:06 ` Patrick Gundlach
2003-03-12 15:09 ` Hans Hagen
2003-03-11 15:02 ` s-mag-01 Adam Lindsay
2003-03-11 20:52 ` s-mag-01 Hans Hagen
2003-03-11 9:13 ` s-mag-01 Patrick Gundlach
2003-03-10 17:00 ` Displayed material, again Hans Hagen
2003-03-10 23:24 ` Hans Hagen
2003-03-11 10:08 ` Giuseppe Bilotta [this message]
2003-03-11 10:52 ` Re[2]: " Hans Hagen
2003-03-11 11:47 ` Re[3]: " Giuseppe Bilotta
2003-03-11 14:57 ` Hans Hagen
2003-03-11 17:04 ` Re[4]: " Giuseppe Bilotta
2003-03-12 20:36 ` Hans Hagen
2003-03-13 9:36 ` Re[5]: " Giuseppe Bilotta
2003-03-13 12:23 ` Hans Hagen
2003-03-11 15:12 ` Re[3]: " Hans Hagen
2003-03-12 21:07 ` Hans Hagen
2003-03-13 9:38 ` 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=793170919.20030311110817@iol.it \
--to=gip.bilotta@iol.it \
--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).