From: Wolfgang Schuster <wolfgang.schuster@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: empty TOC
Date: Mon, 7 Jan 2013 22:21:10 +0100 [thread overview]
Message-ID: <90C383A1-EAE1-4BF0-9A54-07A4D297B8DF@gmail.com> (raw)
In-Reply-To: <50EB3AE7.80004@wxs.nl>
Am 07.01.2013 um 22:15 schrieb Hans Hagen <pragma@wxs.nl>:
> On 1/7/2013 2:11 PM, Peter Rolf wrote:
>> Hi,
>>
>> I get an empty TOC again when compiling the documentation for the drops
>> module. The entries for the TOC are set in the *.tuc file, but the TOC
>> in the document stays empty. I tried the "[criterium=all]" option, same
>> result. A TOC example from the wiki worked, so this time not a general
>> problem. The *.log and the *.tuc file are attached, source can be sent
>> off-list.
>
> small test needed
There is a problem when section blocks are used:
\starttext
\startfrontmatter
\completecontent
\chapter{Intro}
\stopfrontmatter
\startbodymatter
\chapter{One}
\chapter{Two}
\stopbodymatter
\stoptext
Wolfgang
___________________________________________________________________________________
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:[~2013-01-07 21:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 13:11 Peter Rolf
2013-01-07 21:15 ` Hans Hagen
2013-01-07 21:21 ` Wolfgang Schuster [this message]
2013-01-07 21:28 ` Andreas Mang
2013-01-07 22:32 ` 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=90C383A1-EAE1-4BF0-9A54-07A4D297B8DF@gmail.com \
--to=wolfgang.schuster@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).