ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re[5]: In-paragraph display
Date: Tue, 03 Dec 2002 11:46:31 +0100	[thread overview]
Message-ID: <5.1.0.14.1.20021203113956.03313b40@server-1> (raw)
In-Reply-To: <741344773.20021203102556@iol.it>

At 10:25 AM 12/3/2002 +0100, you wrote:
>Tuesday, December 3, 2002 Bruce D'Arcus wrote:
>
> >> 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.
>
>BDA> For what it's worth, I agree with Giuseppe here.   It's the same issue
>BDA> I had with block quotes: that even if there's no blank line, ConTeXt
>BDA> assumes new paragraph.
>
>The blockquote example is a very good example, IMO: an
>"indipendent" (new paragraphed) block quote/quotation/whatever is
>not "conceptually" different from a "displayed" (that doesn't
>start a new paragraph) block quote/quotation/whatever. So there
>should be no need to mark it up differently (as is required by the
>ConTeXt assumption on paragrah breaking).

wait till you enter the area of typesetting a bit more complex docs (in 
terms of typo); then you really want to be able to make the difference; in 
that case, the way an author want it typeset is not the same as the 
designers view; it's not a far way from letting the author determine if 
something should be bold/slanted/whatever instead of coding in terms of 
emphasized/important/interesting, or, what we occasionally see, bolder and 
bigger subsubsection heads than sectionheads -)

now, say that there will be:

(1) quotation
(2) blockquotation

with

(1) forcing a new par
(2) behaving the way you want

and both can be set up as usual to act differently, that would solve the 
problem, wouldn't it, since you could either setup up quotation differently 
or use blockquotation. (i'm not going to change the quotation defaults, 
simply because it would break compatibility)

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
-------------------------------------------------------------------------

  reply	other threads:[~2002-12-03 10:46 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 [this message]
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=5.1.0.14.1.20021203113956.03313b40@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).