ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan BRASLAU <alan.braslau@cea.fr>
To: ntg-context@ntg.nl
Cc: Hans Hagen <pragma@wxs.nl>
Subject: Re: mkiv structure
Date: Thu, 2 Jul 2009 20:34:51 +0200	[thread overview]
Message-ID: <200907022034.51459.alan.braslau@cea.fr> (raw)
In-Reply-To: <4A36001B.8000307@wxs.nl>

On Monday 15 June 2009 10:02:35 Hans Hagen wrote:
>
> I was wondering ... the last time quite some nice small test samples
> were posted for testing the structure code
>

% Example taken from cont-enp.pdf
% However, adding \part{} is problematic...
% (maybe someone can correct this?)
%
\setuppagenumbering[alternative=doublesided,way=bytext,partnumber=no]
\setuphead[part][placehead=yes,resetnumber=no]
\doifmode{mkiv}{
	\setuphead[part][sectionsegments=1:1]
	\setupstructureheads[sectionsegments=2:5]
	}
\setuplabeltext[chapter=Chapter ] \setuplist[chapter][label=yes]
\setuplist[part,chapter,section,subsection,subsubsection]
          [partnumber=no,interaction=all,alternative=c]
	  % number – title – dots – pagenumber

\starttext

\startfrontmatter
	\completecontent
	\chapter{Introduction}		% in content, no number
\stopfrontmatter
\startbodymatter
	\part{Beginning}
	\chapter{First}			% number 1, in content
	\section{Alfa}			% number 1.1, in content
	\section{Beta}			% number 1.2, in content
	\chapter{Second}		% number 2, in content
	\subject{Blabla}		% no number, not in content
	\part{End}
	\chapter{Third}			% number 3, in content
\stopbodymatter
\startappendices
	\chapter{Index}			% letter A, in content
	\chapter{Abbreviations}		% letter B, in content
\stopappendices
\startbackmatter
	\chapter{Acknowlegdement}	% no number, in content
	\title{Colofon}			% no number, not in content
\stopbackmatter

\stoptext

___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2009-07-02 18:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-15  8:02 Hans Hagen
2009-07-02 18:34 ` Alan BRASLAU [this message]
2009-07-02 21:25   ` Hans Hagen
2009-07-03  8:12     ` Alan BRASLAU
2009-07-03 14:04       ` Hans Hagen
2009-07-05  9:32         ` Wolfgang Schuster
2009-07-08  8:28           ` Hans Hagen
2009-07-08 10:10           ` Hans Hagen
2009-07-05 22:20         ` Alan BRASLAU
2009-07-06 11:44           ` Hans Hagen
2009-07-09  7:38       ` Hans Hagen
2009-07-09  7:59         ` Alan BRASLAU
2009-07-09 12:27           ` Wolfgang Schuster
2009-07-09 12:39             ` Hans Hagen
2009-07-02 19:17 ` references (mainlanguage) Alan BRASLAU
2009-07-02 21:07   ` Willi Egger
2009-07-03  7:07     ` Alan BRASLAU
2009-07-02 21:22   ` Hans Hagen

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=200907022034.51459.alan.braslau@cea.fr \
    --to=alan.braslau@cea.fr \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).