From: Mica Semrick <mica@silentumbrella.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Are nested sections possible?
Date: Fri, 11 Mar 2016 00:43:43 -0800 [thread overview]
Message-ID: <85D41ADB-991E-449D-9928-F61591B2C7EC@silentumbrella.com> (raw)
In-Reply-To: <56E28371.6040902@gmx.es>
[-- Attachment #1.1: Type: text/plain, Size: 1575 bytes --]
Hi Pablo,
Sorry for the brevity of my original message, it is quite late.
I'm working on styling an XML dialect, where nesting can go, and often does quite deep, and several different section level elements can be allowed to nest within each other. If nested sections were possible, I wouldn't have to write code to try and figure out how deep a nested is; ConTeXt would know and would number the sections accordingly.
-m
On March 11, 2016 12:36:01 AM PST, Pablo Rodriguez <oinos@gmx.es> wrote:
>On 03/11/2016 09:08 AM, mica@silentumbrella.com wrote:
>> Greetings,
>>
>> Is it possible to have
>> [...]
>> render as:
>>
>> 1. Hey a chapter!
>> 1.1 something.one
>> 1.1.1 something.one.one
>> 1.1.1.1 something.one.one.one
>
>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.)
>
>Let me know what I am missing. Best wishes,
>
>Pablo
>--
>http://www.ousia.tk
>___________________________________________________________________________________
>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
>___________________________________________________________________________________
[-- Attachment #1.2: Type: text/html, Size: 1526 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-03-11 8:43 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 [this message]
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
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=85D41ADB-991E-449D-9928-F61591B2C7EC@silentumbrella.com \
--to=mica@silentumbrella.com \
--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).