From: Tobias Burnus <burnus@net-b.de>
Subject: Re: compiling project files
Date: Wed, 09 Aug 2006 18:26:52 +0200 [thread overview]
Message-ID: <44DA0CCC.9000104@net-b.de> (raw)
In-Reply-To: <221cc89e0608090852s616e2ecag3a8e21cd3b679b02@mail.gmail.com>
Hi Derek,
Derek Schmidt wrote:
> When I texexec it, it runs but only produces and empty table of contents with the word Contents at the top. It won't list the chapters, forget about actually printing their content.
>
I have only three ideas:
(a) The data is not available. The mechanism is a follows:
1. TeX is run and chapter names with pagenumbers etc. are saved into
<jobname>.tui.
2. TeXutil is run and sorts some entries in *.tui and writes *.tuo
3. TeX is run again, reads .tuo and uses that data to produce the table
of contents etc. (and produces a new .tui)
As this changes the page numbers (for longer table of contents), TeXutil
and TeX are re-run again.
In principle TeXExec should do this automatically. Do you have a *.tuo file?
(b) The data is available via .tuo but somehow \completecontent only
writes the sections below the "Content" chapter, which is empty.
Try: \completecontent[criterium=all]
this instructs it to print the table of content for all chapters (which
is actually the default).
(c) Something is broken (whatever, the installation, ConTeXt/TeXexec, my
ability to find the cause of problems etc.)
Tobias
next prev parent reply other threads:[~2006-08-09 16:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 15:52 Derek Schmidt
2006-08-09 16:26 ` Tobias Burnus [this message]
2006-08-09 16:27 ` Aditya Mahajan
2006-08-13 3:39 ` Derek Schmidt
2006-08-13 15:46 ` Mojca Miklavec
2006-08-14 20:44 ` Peter Münster
2006-08-15 20:16 ` Boris Tschirschwitz
2006-08-15 20:29 ` Aditya Mahajan
2006-08-16 15:58 ` Mojca Miklavec
2006-08-16 16:07 ` Taco Hoekwater
2006-08-16 22:52 ` 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=44DA0CCC.9000104@net-b.de \
--to=burnus@net-b.de \
--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).