ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: the closing bracket (structuring syntax)
Date: Thu, 10 Aug 2006 22:44:41 +0200	[thread overview]
Message-ID: <44DB9AB9.4000809@wxs.nl> (raw)
In-Reply-To: <D277C0E6-989A-4170-B2DD-B83A2A0BD4CF@st.estfiles.de>

Steffen Wolfrum wrote:
> Hi,
>
> in XML and alike there is a concept of dedicated start/stop in  
> formatting:
>
> <begin heading> ... <end heading >
> <begin footnote> ... <end footnote >
> <begin italic> ... <end italic>
>
> But in ConTeXt/TeX we have always the same closing syntax "}". That  
> makes reading the code not easier.
>
> Is there a workaround to define the closing more precisely (like the  
> examples above),
> so that finding a "}" in a ConTeXt source lets me distinguish what  
> it's about?
>
> But in such a way that the file still can be processed as a regular  
> ConTeXt file?
>   
its' no problem to define most commands as start/stop, however keep in 
mind that some start/stop constructs (like tables) pick up pieces in 
order to store them

so, if some commands need start/stop variants ... just make me a list 
and we'll see what we can do about it

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.com
                                             | www.pragma-pod.nl
-----------------------------------------------------------------

  reply	other threads:[~2006-08-10 20:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-10 19:46 Steffen Wolfrum
2006-08-10 20:44 ` Hans Hagen [this message]
2006-08-10 20:52   ` Steffen Wolfrum
2006-08-10 20:47 ` Aditya Mahajan
2006-08-13 13:29   ` Steffen Wolfrum
2006-08-14  6:13     ` Steffen Wolfrum
2006-08-15 14:30       ` Aditya Mahajan
2006-08-14 22:26     ` Aditya Mahajan
2006-09-13  2:34       ` Aditya Mahajan

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=44DB9AB9.4000809@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).