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

At 01:37 AM 12/3/2002 +0100, you 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.

it's because in my limited perception display stuff is not part if the par -)

>But I have to specify it manually. If I later decide to rewrite
>the stuff so that it's really in separate paragraphs I have to
>change the displayed environment, while what should suffice is
>letting ConTeXt understand that a new paragraph is started --the
>*standard* way (empty line).

eh .. not sure if i understand this; some global switch would do most of 
the trick i assume

> >>Doesn't work. Try setting \setupindenting[medium] in your example;
> >>you'll notice that each line starts a new paragraph, and this is
> >>not what is wanted.
>
>HH> ah, so we should look ahead, doable but never 100% robust; with 
>regards to
>HH> looking back, definitely less robust
>
>I don't think there should be any need to look back or ahead. Just
>don't force a new paragraph before and after each displayed item.
>Let the user choose, the standard way(s).

well, since i want to be able to control consistency, i do need to look 
back; say that the design says: no empty lines (parskips) before something, 
then i need to configure that particular display instance to ignore the 
(possiibly already applied) parskip; keep in mind that it's not always the 
author who decides that somethign should start like a new paragraph; so, 
even if i provide you thsi display feature, i need it to be configurable in 
many ways for my own needs -)  would not hurt you anyway

> >>I propose a global switch like
> >>
> >>\setupstartstops[break=always] % current ConTeXt behaviour
> >>\setupstartstops[break=par]    % only start new paragraphs
> >>                                % when there are empty lines
>
>HH> hm, not sure it it hooks/should hook into start/stop
>
>Where should it hook? All displayed items are start/stop pairs. If
>you want to overrule this for a specific start/stop pair, you can
>always to it with the local switch:

i cannot simply before=\startdisplay things because it would break 
compatibility, so it would mean that each environment would get a 
display=... switch with some global default, in addition to start/stop

>is part of a paragraph but gets "highlited" by typesetting it in a
>different format, sort of like a subparagraph. This category
>includes itemizations (all itemgroups, actually), formulas (not
>inline, of course), quotations, etc.

hm, i like a more general view on 'display': anything that stands out in 
the text stream, being par or not, this is why it should be configurable 
(even tex is a bit fuzzy about it, since display math is used for both 
in-par or between par math)

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

  parent reply	other threads:[~2002-12-03 11:00 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           ` Re[3]: " Simon Pepping
2002-12-03 11:00         ` Hans Hagen [this message]
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.20021203115211.02275738@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).