From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: nomarking function in MKIV
Date: Thu, 1 Jul 2010 12:23:01 +0200 [thread overview]
Message-ID: <AANLkTimfymsksEPIEdbGH5_vC1RSGQGRpKlPrxAYFTMH@mail.gmail.com> (raw)
In-Reply-To: <E62F48E7-6B56-4E01-AA28-F1865E44BB2E@uni-bonn.de>
On Thu, Jul 1, 2010 at 12:00 PM, Thomas A. Schmitz
<thomas.schmitz@uni-bonn.de> wrote:
>
> On Jul 1, 2010, at 11:44 AM, Alan BRASLAU wrote:
>
>> No one has answered my question about to what belongs any text
>> between a proceding \stopchapter and a following \startchapter, as in
>> \startchapter{title}
>> \stopchapter
>> some text
>> \startchapter{next title}
>> \stopchapter
>
> Excuse me, but your question is just plain nonsense. What you show us is sloppy writing. Why should ConTeXt or any other system cater to this? You're asking "where does text belong that doesn't belong to any hierarchical structure of my document?" The answer is obvious: this text doesn't belong anywhere.
well, to avoid black hole we can say that
"some text"
belongs to the parent section of chapter (part in this case or section0)
which actually is "virtual" , ie almost doesn't influences output.
So one can think to an endless chain
... section-2 > section-1 > section0 aka 'part' > section1 'aka' chapter ...
where 'a > b' mean a is parent of b
For "virtual" consider
\starttext
\chapter{foo}
\subsection{goo}
\stoptext
where there is a virtual \section .
More or less (maybe less than more) .
--
luigi
___________________________________________________________________________________
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:[~2010-07-01 10:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 16:14 John Devereux
2010-06-29 17:33 ` Peter Münster
2010-06-29 21:03 ` John Devereux
2010-06-30 8:19 ` Alan BRASLAU
2010-06-30 9:03 ` Peter Münster
2010-06-30 10:03 ` nomarking function in MKIV (selector) Alan BRASLAU
2010-06-30 22:35 ` nomarking function in MKIV Wolfgang Schuster
2010-07-01 8:16 ` Alan BRASLAU
2010-07-01 8:30 ` Wolfgang Schuster
2010-07-01 9:23 ` Peter Münster
2010-07-01 9:44 ` Alan BRASLAU
2010-07-01 9:55 ` luigi scarso
2010-07-01 10:00 ` Thomas A. Schmitz
2010-07-01 10:23 ` luigi scarso [this message]
2010-07-01 18:59 ` Alan BRASLAU
2010-07-02 8:18 ` Thomas A. Schmitz
2010-07-02 9:18 ` luigi scarso
2010-07-02 11:07 ` Alan BRASLAU
2010-07-01 10:11 ` Henning Hraban Ramm
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=AANLkTimfymsksEPIEdbGH5_vC1RSGQGRpKlPrxAYFTMH@mail.gmail.com \
--to=luigi.scarso@gmail.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).