ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: John Culleton <john@wexfordpress.com>
Subject: Re: A proposal for the sectioning commangs
Date: Fri, 21 Jun 2002 11:27:50 -0400	[thread overview]
Message-ID: <200206211127.50412.john@wexfordpress.com> (raw)
In-Reply-To: <1809370081.20020621154616@bigfoot.com>

On Friday 21 June 2002 09:46 am, Giuseppe Bilotta wrote:
> Hello,
>
> one of the main features of both ConTeXt and LaTeX over plain TeX
> is their heavily "object-oriented" approach to source writing,
> giving a large set of useful tools to build well-structured
> documents.
>
> There is though one aspect which has not been addressed in either:
> structuring of the sections. One still uses \chapter, \section,
> \subsection etc to denote the start of any of these, while
> structured writing would call for \startchapter ... \stopchapter,
> \startsection ... \stopsection etc.
>
In my very humble opinion this is a big part of the problem with tools
such as XML and its children. Using two tags where one will do is just
excessive clutter, and ends up with lines like
\stopsubusubsection \stopsubsection \stopsection \stopchapter
.... which is all superfluous code and offers the chance for keying errors on 
every tag.  The computer is smart enough to know that a \chapter head 
terminates all previous subordinate levels. And the person reading the code 
is smart enough too. I see no virtue in this proposal. 

No matter how elegant the code looks, in fact it is just a means to an end, 
and the end is a publication, and all those meaningless stop tabs won't
afffect the final document in any case. 

Just my 2 centavos.

John Culleton
(programming since 1968, and it shows.)

__________________________________________________
D O T E A S Y - "Join the web hosting revolution!"
             http://www.doteasy.com


  reply	other threads:[~2002-06-21 15:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-21 13:46 Giuseppe Bilotta
2002-06-21 15:27 ` John Culleton [this message]
2002-06-21 21:15   ` Re[2]: " Giuseppe Bilotta
2002-06-21 22:37     ` Duncan Hothersall
2002-06-22  2:24       ` John Culleton
2002-06-23 21:47     ` Re[2]: " Hans Hagen
2002-06-23 10:45   ` Hans Hagen
2002-06-21 16:01 ` A proposal for the sectioning commands--addendum John Culleton
2002-06-21 21:17   ` Re[2]: " Giuseppe Bilotta
2002-06-23 19:39   ` Hans Hagen
2002-06-23 21:42     ` Re[2]: " Giuseppe Bilotta
2002-06-24  8:40       ` Hans Hagen
2002-06-24  8:55         ` Re[3]: " Giuseppe Bilotta
2002-06-24 18:06           ` texedit (was: something else) Henning Hraban Ramm
2002-06-25 15:47             ` Hans Hagen
2002-06-26 18:43               ` Henning Hraban Ramm
2002-06-27 16:54                 ` Hans Hagen
2002-06-28 21:48                   ` Henning Hraban Ramm
2002-06-23 10:43 ` A proposal for the sectioning commangs Hans Hagen

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=200206211127.50412.john@wexfordpress.com \
    --to=john@wexfordpress.com \
    /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).