ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: decriptions
Date: Sun, 27 Jun 1999 01:03:52 +0200	[thread overview]
Message-ID: <37755C58.A25355EE@wxs.nl> (raw)
In-Reply-To: <199906262109.XAA03376@servalys.hobby.nl>

Wybo Dekker wrote:

> Another question about the new description environment: before
> > \stopdescriptions
> an empty line appears to be required. Is that a bug or a feature?
> Without it, tex says that it inserted a missing }

This is one the few situations that context expects a \par or empty
line. It has to do with the fact that the par is grabbed, which in
itself is due to the fact that one can set the font. Consider 

\description{text} more text in some specific font 

some text not belonging to the description in the main body font. 

There is no robust way to deal with this. 

In general, one can set up a text rather spacy in context, because quite
some effort went into catching those situations. 

So, it's a nuisance, due to a feature. 

Hans

-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.nl
-----------------------------------------------------------------


      reply	other threads:[~1999-06-26 23:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-25 11:39 decriptions Hans Hagen
1999-06-25 13:48 ` decriptions Taco Hoekwater
1999-06-25 11:53   ` decriptions Hans Hagen
1999-06-26 10:37 ` decriptions Wybo Dekker
1999-06-26 15:54   ` decriptions Hans Hagen
1999-06-26 21:09 ` decriptions Wybo Dekker
1999-06-26 23:03   ` Hans Hagen [this message]

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=37755C58.A25355EE@wxs.nl \
    --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).