ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re[2]: In-paragraph display
Date: Mon, 02 Dec 2002 18:40:46 +0100	[thread overview]
Message-ID: <5.1.0.14.1.20021202183104.02d46b78@server-1> (raw)
In-Reply-To: <1073357918.20021202180316@iol.it>

At 06:03 PM 12/2/2002 +0100, you wrote:

>Uhm. I can't think of any example like that, really. The point is
>that in ConTeXt as it is now a display (formula, itemization,
>quotation, etc) is always forces a paragraph before and after,
>which is not consistent with what the writer might want; think for
>example of something like:

hm, but it's not the writer who's in charge here, but the designer; so, in 
terms of intentional coding, one should code in such a way that whatever 
strange thing happens along the road (accidental empty line or not) the 
output is consistent. So, an in-par something should be coded as such so 
that the environment can handle it, as good as possible.

>--------------
>An introduction to the following:
>* itemization
>* one more item
>and a conclusion, all in the same paragraph

there are options for that -)

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

ah, so we should look ahead, doable but never 100% robust; with regards to 
looking back, definitely less robust

>(1) the display should end the previous paragraph if and only if
>\start... is preceded by an empty line
>
>(2) the material following the \stop... should start a new
>paragraph if and only if there is an empty line between the \stop
>and the material

or a

text\par text, or

text\whow[expanding into \par]text

>HH> The best solution of course is to define the proper instances of
>HH> enviroments (math already has 'm)
>
>All (displayed) blocks should have this feature. If you don't want
>to break backwards compatibility, you could setup a couple of

you can bet on that

>options for \startstop pairs. As I proposed in another mail, it
>should be tunable at a global level and on a per-\startstop level:

such a feature should be tested for *each* environment with all kind of 
combinations, since spacing can really become nasty

>I propose a global switch like
>
>\setupstartstops[break=always] % current ConTeXt behaviour
>\setupstartstops[break=par]    % only start new paragraphs
>                                % when there are empty lines

hm, not sure it it hooks/should hook into start/stop

>and local switches like:
>
>\setupquotations[newpar=always] % current behaviour
>
>where newpar can be always, (current behaviour, regardless of
>global setting), default (follow general \startstop behaviour set
>up by \setupstartstops) or par (start according to empty lines
>regardless of global setting). Does it sound sensible?

depends, this is not something that will be there in-a-minute, and i 
definitely don't want to break compatibility for a convenience over coding 
feature -)

The first thing is a proper \start/stopdisplay pair, so let's start with 
that; one can then hook that into start/stop an dlater we can see if some 
kind of auto-display is possible [display=none|before|after|both] or so

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-02 17:40 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 [this message]
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
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.20021202183104.02d46b78@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).