From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Are nested sections possible?
Date: Thu, 24 Mar 2016 22:08:00 +0100 [thread overview]
Message-ID: <56F45730.1010008@wxs.nl> (raw)
In-Reply-To: <56E84203.40600@uni-bonn.de>
On 3/15/2016 6:10 PM, Thomas A. Schmitz wrote:
> On 03/15/2016 05:54 PM, Alan BRASLAU wrote:
>> Indeed, Hans, it would be nice to be able to nest sectionlevels within
>> a chapter...section... scheme (which is NOT depreciated, although
>> antiquated).
>
> Oooh, shiny! In the TEI community, there are also people who repeat that
> having <div>s all the way down is modern, and <div1><div2> etc. is old
> hat. Well, I like to think about the way I structure my texts before I
> write them. I'm old fashioned that way...
>
> But seriously: by all means, let's allow nesting. But don't let anyone
> tell you that explicit names are "antiquated." They make TeX or xml
> source documents so much more readable! And when you have to retrace
> five levels of \startsectionlevels because you want to change the
> structure of your document, you will rue the day you abandoned proper
> names.
they are not antiquated at all
the main benefit from using \startchapter ... \stopchapter instead of
\chapter is that we then know where something end which is handy when
you want to finish things before starting something new (esp when
grouping is involved it can get messy otherwise) ... it's also easier on
the export
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-03-24 21:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 8:08 mica
2016-03-11 8:23 ` josephcanedo
2016-03-11 8:36 ` Pablo Rodriguez
2016-03-11 8:43 ` Mica Semrick
2016-03-12 0:53 ` Alan BRASLAU
2016-03-14 8:05 ` Procházka Lukáš Ing.
2016-03-15 16:54 ` Alan BRASLAU
2016-03-15 17:10 ` Thomas A. Schmitz
2016-03-15 19:09 ` Alan BRASLAU
2016-03-24 21:11 ` Hans Hagen
2016-03-24 21:08 ` Hans Hagen [this message]
2016-03-14 8:52 ` Pablo Rodriguez
2016-05-20 4:39 ` docent.einstein
2016-03-11 9:37 ` Andreas Schneider
2016-03-11 9:43 ` Hans Hagen
2016-03-11 15:42 ` Mica Semrick
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=56F45730.1010008@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).