ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan BRASLAU <alan.braslau@cea.fr>
To: ntg-context@ntg.nl
Subject: Re: \setuphead and \startchapter request
Date: Mon, 19 Mar 2012 16:16:21 +0100	[thread overview]
Message-ID: <20120319161621.36d03e4d@sole.extra.cea.fr> (raw)
In-Reply-To: <2CE176E8-AD54-4498-A495-ADA5EE90AE68@googlemail.com>

Wolfgang,

Thank you for the suggestions.
However, I have tried many such, things...



On Mon, 19 Mar 2012 12:50:14 +0100
Wolfgang Schuster <schuster.wolfgang@googlemail.com> wrote:

> 
> Am 19.03.2012 um 12:45 schrieb Alan BRASLAU:
> 
> > I would like to use, for example,
> > 
> > \setuphead [chapter] [after={\placecontent\blank}]
> > 
> > But sometimes, I would like to use something like
> > 
> > \startchapter [number=no,incrementnumber=no,after=,
> > 	title={Conclusions of the first part}]
> > 
> > \stopchapter
> 
> You know \starttitle, it’s the unnumbered version of \startchapter.

Yes, of course, but \starttitle does not, by design, add an entry
to the TOC, nor a bookmark. And

\starttitle [title={Conclusions}]
\writetolist[chapter]{}{Conclusions}% works
\bookmark{Conclusions}% Does not work!

is less elegant than

\startchapter [number=no,incrementnumber=no,title={Conclusions}]

(but does have the advantage of suppressing the "Chapter" label.)


> We have the following key for \setuphead:
> 
> - beforesection (called before \startchapter),
> - insidesection (called after \startchapter) and
> - aftersection (called after \stopchapter)

You suggest that I use insidesection={\placecontent\blank}
rather than after={\placecontent\blank}. OK, this works.

However, in both cases, the contents get placed after the above
\starttitle (or \startchapter) commands, something that one really does
not want. Alternately, adding \placecontent\blank everywhere else is
sloppy.


> > 2. If I have:
> > \setuplabeltext [chapter=Chapter ] % with trailing space; blank by
> > default would there be some way to specify chapter=, (or another
> > mechanism) to have the Chapter label blank for a specific instance
> > of \startchapter?
> 
> The easiest way is to create a new heading for this purpose.

I do not really want to create new headings for this purpose,
if I can avoid it, and should be unnecessary.
The suggestion would be for specific instances of \startchapter etc.
to be able to take \setuphead keywords as local definitions.

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
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2012-03-19 15:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19 11:45 Alan BRASLAU
2012-03-19 11:50 ` Wolfgang Schuster
2012-03-19 15:16   ` Alan BRASLAU [this message]
2012-03-19 16:09     ` Wolfgang Schuster

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=20120319161621.36d03e4d@sole.extra.cea.fr \
    --to=alan.braslau@cea.fr \
    --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).