From: John Culleton <john@wexfordpress.com>
Subject: Re: A proposal for the sectioning commangs
Date: Fri, 21 Jun 2002 22:24:43 -0400 [thread overview]
Message-ID: <200206212224.43489.john@wexfordpress.com> (raw)
In-Reply-To: <f0206212327230ABA@capdm.com>
On Friday 21 June 2002 06:37 pm, Duncan Hothersall wrote:
> > 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.
>
> Consider a section which contains some content, followed by a subsection,
> followed by more content in the same section. I would tend to set this with
> vertical space indicating the end of the subsection. Without an explicit
> \stop the additional content of the section could belong either to the
> section or the subsection.
>
> For me it isn't a problem, because I master in XML and create ConTeXt code
> from the XML using OmniMark. But for those using ConTeXt as a master format
> it must be quite important.
>
> dh
I have never seen the kind of confuguration you describe. It is possible
I suppose. In general if my \section is subdvided it is completely subdivided.
Or there might be some introductory text right after the \section header and
before the first \subsection header. But returning to the same section after
a subsection would be difficult to configure. How would you indicate this
to a reader? would you put in an additional header line such as
``Section 22 (continued)''? Or are you using indentation for each level
of subdivision?
Perhaps you could give an example of how it would appear to the reader.
After all the mumbo jumbo one ends up with a document (either paper
or electronic) that some human being has to interpet and make some sense of.
A section with a subsection embedded in the middle of its text would be
difficult indeed to interpet.
John Culleton
__________________________________________________
D O T E A S Y - "Join the web hosting revolution!"
http://www.doteasy.com
next prev parent reply other threads:[~2002-06-22 2:24 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
2002-06-21 21:15 ` Re[2]: " Giuseppe Bilotta
2002-06-21 22:37 ` Duncan Hothersall
2002-06-22 2:24 ` John Culleton [this message]
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=200206212224.43489.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).