From: Julian Becker <becker.julian@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Continuous chapter numbering without prefixes in documents with parts
Date: Fri, 1 Jul 2011 15:33:07 +0200 [thread overview]
Message-ID: <BANLkTikBNfMVB0m-8YUTjbSwN+6UDxCu8g@mail.gmail.com> (raw)
In-Reply-To: <web-7540344@be2.uni-bonn.de>
[-- Attachment #1.1: Type: text/plain, Size: 2042 bytes --]
Thank you Thomas, and sorry for not having performed a proper search
priorly.
Still, the thread you refered me to only provides half of what I need (if I
didn't miss anything):
I added the line:
\setuphead[chapter][chaptersegments=chapter]
which indeed got rid of the chapter number prefix.
Still, the chapter numbering gets reset in each new part. How can I avoid
that?
Julian
2011/7/1 Thomas Schmitz <tschmit1@uni-bonn.de>
> On Fri, 1 Jul 2011 15:02:22 +0200
> Julian Becker <becker.julian@gmail.com> wrote:
>
>> Does anybody know how to implement a continuous numbering of chapters in
>> documents with several parts?
>>
>> More specifically: how can I achieve the following numbering scheme (with
>> unprefixed chapter numbers):
>> I First part
>> 1 Chapter one
>> 2 Chapter two
>> II Second part
>> 3 Chapter three
>>
>>
>> I tried (unsuccessfully) the following:
>>
>> \setuphead[part][placehead=yes]
>> \starttext
>> \part{First part}
>> \chapter{Chapter one}
>> \chapter{Chapter two}
>> \part{Second part}
>> \chapter{Chapter three}
>> \stoptext
>>
>> The here result is something like:
>> First part
>> 1.1 Chapter one
>> 1.2 Chapter two
>> Second part
>> 2.1 Chapter three
>>
>>
>> I tried to get rid of the chapter prefixes by putting
>> \setuphead[chapter][prefix=no]
>> but that had no effect whatsoever.
>>
>> Any ideas?
>>
>
> Yes: search the list; the same question was asked three weeks ago, together
> with a solution:
> http://archive.contextgarden.net/message/20110619.234245.2e8ee926.en.html
>
> Thomas
>
> ___________________________________________________________________________________
> 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: 3208 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:[~2011-07-01 13:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 13:02 Julian Becker
2011-07-01 13:16 ` Thomas Schmitz
2011-07-01 13:33 ` Julian Becker [this message]
2011-07-01 14:14 ` Thomas Schmitz
2011-07-07 8:12 ` Julian Becker
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=BANLkTikBNfMVB0m-8YUTjbSwN+6UDxCu8g@mail.gmail.com \
--to=becker.julian@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).