From: Ulf Martin <ulfmartin@web.de>
Subject: Re: continuous numbering of subsection
Date: Sun, 25 Jun 2006 19:36:33 +0200 [thread overview]
Message-ID: <449EC9A1.8040601@web.de> (raw)
In-Reply-To: <449EBCE9.6080200@wxs.nl>
Hi
Hans Hagen schrieb:
> \setuphead [chapter][resetnumber=no]
> \setupsection[section][previousnumber=no]
Ok, I undestand. I apologise that my example was too short. I'd like to
have things more flexible:
If an arbitrary and irregular number of levels is introduced (sections,
subsections, etc., numbered hierarchically as usual), the topic
numbering should remain continuous and unaffected
(that's why I thought, a separate definition, as in
\definehead[topic][...], would be appropriate).
Conceptually, though, "topic" is a section-like subdivision, so, for
example, should appear in the TOC.
This is typical e.g. in (German) law texts (here with "§" as a topic
marker but this is not the point), Example:
I. ... "Chapter"
§ 1 ...
1 ... "Section"
§ 2 ... Topic in section
1.1 ... "Subsection"
§ 3 ... Topic in subsection
§ 4 ...
1.2 ...
§ 5 ...
2 ...
§ 6 ...
§ 7 ...
2.1 ...
§ 8 ...
II. ...
§ 9 ... Topic in chapter
1 ...
§ 10 ...
§ 11 ...
1.1 ...
§ 12 ...
Of course, referencing, entry in TOC, index etc. should be correct.
It would be even more preferable if one could "attach" the topic
numbering to a specified level, say, chapters. The above example then
would become:
I. ... "Chapter"
§ 1 ... Topic in chapter
1 ... "Section"
§ 2 ... Topic in section
1.1 ... "Subsection"
§ 3 ... Topic in subsection
§ 4 ...
1.2 ...
§ 5 ...
2 ...
§ 6 ...
§ 7 ...
2.1 ...
§ 8 ...
II. ...
§ 1 ... First topic in second chapter
1 ...
§ 2
§ 3
1.1 ...
§ 4 ...
Thank you & sorry for the incomplete first question!
Ulf
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2006-06-25 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-25 15:50 Ulf Martin
2006-06-25 16:42 ` Hans Hagen
2006-06-25 17:36 ` Ulf Martin [this message]
2006-06-26 7:23 ` Ulf Martin
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=449EC9A1.8040601@web.de \
--to=ulfmartin@web.de \
--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).