From: Giuseppe Bilotta <gip.bilotta@iol.it>
Cc: ntg-context@ntg.nl
Subject: Re[2]: About itemize
Date: Tue, 12 Nov 2002 00:46:35 +0100 [thread overview]
Message-ID: <3227349646.20021112004635@iol.it> (raw)
In-Reply-To: <5.1.0.14.1.20021112002309.031bcd80@remote-1>
HH> first of all, we're not dealing with a bug, it's a feature; so, if some
HH> other behavior is wanted, it should be an option of extension to existing
HH> mechanisms, nog a replacement.
HH> there is one thing we should keep in mind: naive users are not always aware
HH> of tex's empty line == par, so this is why \start/\stop things are
HH> consistent in absense or presense of them;
HH> distinguishing between display and semi-display is therefore not that
HH> trivial, and the best option is separate environments, like
HH> \startquotation ... \stopquotation
HH> (or \startdquotation ... \stopdquotation for display quotation) versus
HH> \startpquotation ... \stoppquotation
HH> for an in-paragraph one (like we have with formulas, see core-mat.tex)
HH> that way, one knows what to expect, since it's clear from the coding, and
HH> not from a (forgotten, or accidental) empty line
HH> another option is to have a dedidated environment
HH> \startinparagraph ... \stopinparagraph
HH> or \startcontinue ... \stopcontinue
HH> which nills the surrounding whitespace and inhibits the next indent. (this
HH> should be not that hard to implement)
This latter alternative sounds awfully 'redundant' (too much code
for a simple thing); the first sounds somewhat better, but the
best solution IMO is to have an option/conditional \obeypars or
something like that. When true, empty lines after startstops
denote paragraph and lack of empty lines denote "remaining in the
same paragraph"; when false, current ConTeXt behaviour is kept.
Maybe we may want to have a per-startstop option
(obeypars=true,obeypars=false) together/in place of the global
\obeypars/\noobeypars (or \obeyparstrue/\obeyparsfalse).
Let's say that the best thing (again IMO) is to have a global
option, overridable in each startstop: the obeypars key in
startstops would then accept the values true (force true), false
(force false), default (behave according to the global setting).
Does this sound sensible?
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2002-11-11 23:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-11 21:14 Idris S Hamid
2002-11-11 21:31 ` Giuseppe Bilotta
2002-11-11 23:33 ` Hans Hagen
2002-11-11 23:46 ` Giuseppe Bilotta [this message]
2002-11-12 8:14 ` Re[2]: " Hans Hagen
2002-11-12 14:08 ` Re[3]: " Giuseppe Bilotta
2002-11-12 18:13 ` Hans Hagen
2002-11-12 22:12 ` Re[4]: " Giuseppe Bilotta
2002-11-13 8:40 ` Hans Hagen
2002-11-13 11:32 ` Re[5]: " Giuseppe Bilotta
2002-11-14 2:54 ` Idris S Hamid
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=3227349646.20021112004635@iol.it \
--to=gip.bilotta@iol.it \
--cc=ntg-context@ntg.nl \
--cc=ntg-context@ref.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).