From: <docent.einstein@centrum.cz>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Are nested sections possible?
Date: Fri, 20 May 2016 06:39:04 +0200 [thread overview]
Message-ID: <20160520063904.472B7BB5@centrum.cz> (raw)
In-Reply-To: 00070000924800921778036232d6
[-- Attachment #1.1: Type: text/plain, Size: 3474 bytes --]
Zdravim Lukasi,
Nejsem si jisty, zda se nemylim, ale pokud jsi z Brna, pak bych Te rad pozdravil.
Radek Pysny
______________________________________________________________
> Od: Procházka Lukáš Ing. <LPr@pontex.cz>
> Komu: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
> Datum: 14.03.2016 09:05
> Předmět: Re: [NTG-context] Are nested sections possible?
>
Hello,
one more thing:
It would be nice to allow mixing:
- \section like commands (or \startsection ... \stopsection)
- AND \startsectionlevel ... \stopsectionlevel.
The main problem is that one may NEED to mix:
- (ancient) source files which use \section (deprecated) style
- with more versatile \start-\stopsectionlevel style in newer source files.
See the test attached - only the case 3 works universally with the \start-\stopstructurelevel;
any mixing of sectioning styles doesn't yield a desired result.
Best regards,
Lukas
On Sat, 12 Mar 2016 01:53:18 +0100, Alan BRASLAU <alan.braslau@cea.fr> wrote:
> On Fri, 11 Mar 2016 09:36:01 +0100
> Pablo Rodriguez <oinos@gmx.es> wrote:
>
>> Sorry, Mica, but which is the gain in nesting sections (whether
>> possible or not) over using subsections and subsubsections?
>>
>> I can hardly imagine the sense in the point you’re making. (Sorry, it
>> must be my fault.)
>
> Think about including source in another source, for example.
>
> Say one has an article that becomes a book, or gets included in a book,
> or the book gets parts. In the course of writing, one might decide to
> add an additional level of structure and not want to change all of the
> \start...\stop structure definitions.
>
> In fact, using fixed section, subsection, subsubsection is a bit
> antiquated, isn't it?
>
> Alan
> ___________________________________________________________________________________
> 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 <http://www.ntg.nl/mailman/listinfo/ntg-context>
> webpage : http://www.pragma-ade.nl <http://www.pragma-ade.nl> / http://tex.aanhet.net <http://tex.aanhet.net>
> archive : http://foundry.supelec.fr/projects/contextrev/ <http://foundry.supelec.fr/projects/contextrev/>
> wiki : http://contextgarden.net <http://contextgarden.net>
> ___________________________________________________________________________________
--
Ing. Lukáš Procházka | mailto:LPr@pontex.cz
Pontex s. r. o. | mailto:pontex@pontex.cz | http://www.pontex.cz <http://www.pontex.cz>
Bezová 1658
147 14 Praha 4
Tel: +420 241 096 751
Fax: +420 244 461 038
----------
___________________________________________________________________________________
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 <http://www.ntg.nl/mailman/listinfo/ntg-context>
webpage : http://www.pragma-ade.nl <http://www.pragma-ade.nl> / http://tex.aanhet.net <http://tex.aanhet.net>
archive : http://foundry.supelec.fr/projects/contextrev/ <http://foundry.supelec.fr/projects/contextrev/>
wiki : http://contextgarden.net <http://contextgarden.net>
___________________________________________________________________________________
[-- Attachment #1.2: Type: text/html, Size: 4658 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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-05-20 4:39 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
2016-03-14 8:52 ` Pablo Rodriguez
2016-05-20 4:39 ` docent.einstein [this message]
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=20160520063904.472B7BB5@centrum.cz \
--to=docent.einstein@centrum.cz \
--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).