ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Bruce D'Arcus" <bdarcus@fastmail.fm>
Subject: Re: Re[3]: In-paragraph display
Date: Mon, 2 Dec 2002 20:18:06 -0500	[thread overview]
Message-ID: <13EC3A06-065D-11D7-B956-0030657A7050@fastmail.fm> (raw)
In-Reply-To: <532276393.20021203013702@iol.it>


On Monday, December 2, 2002, at 07:37 PM, Giuseppe Bilotta wrote:

> HH> hm, but it's not the writer who's in charge here, but the 
> designer; so, in
> HH> terms of intentional coding, one should code in such a way that 
> whatever
> HH> strange thing happens along the road (accidental empty line or 
> not) the
> HH> output is consistent. So, an in-par something should be coded as 
> such so
> HH> that the environment can handle it, as good as possible.
>
> This is where we differ. After all, the empty line is the
> *standard* TeX (and ConTeXt) way to denote new paragraph. While
> should it be different for displayed items? It's inconsistent.

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.

--
Dr. Bruce D'Arcus
Miami University
Geography Department
216 Shideler Hall
Oxford, OH 45056

  reply	other threads:[~2002-12-03  1:18 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 [this message]
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           ` Re[3]: " Simon Pepping
2002-12-03 11:00         ` 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=13EC3A06-065D-11D7-B956-0030657A7050@fastmail.fm \
    --to=bdarcus@fastmail.fm \
    --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).