From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Newbie question on \completecontent
Date: Wed, 06 Aug 2003 21:43:21 +0200 [thread overview]
Message-ID: <5.2.0.9.1.20030806214145.02eacbb8@server-1.pragma-net.nl> (raw)
In-Reply-To: <5E8A3844-C809-11D7-8891-000A95901A7E@rna.nl>
At 14:27 06/08/2003 +0200, you wrote:
>Suppose I create this document:
>
>>\starttext
>>\completecontent
>>\chapter{One}
>>\input tufte
>>\chapter{Two}
>>\input douglas
>>\stoptext
>
>I get a document with a content list and two chaqpters. Now I want to do
>the same in a project. I take the example from the manual and do this:
>
>>%%
>>%% This is the file book.tex
>>%%
>>\startproduct book
>>\project teoade
>>
>>\startfrontmatter
>> \completecontent
>>\stopfrontmatter
>>
>>\startbodymatter
>> \component chapters/chapter1
>> \component chapters/chapter2
>>\stopbodymatter
>>
>>\startbackmatter
>> \completeindex
>>\stopbackmatter
>>\stopproduct
>
>I get the chapters allright, but the list of contents and the index are
>empty. Why?
because they are produced on a per section basis depending on where you
call for them (for instance, in a chapter you can say \placelist[section]
and get a locat toc)
\completecontent[way=bytext]
gives you a document one
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
prev parent reply other threads:[~2003-08-06 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 12:27 Gerben Wierda
2003-08-06 14:52 ` Matthias Weber
2003-08-06 19:43 ` Hans Hagen [this message]
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=5.2.0.9.1.20030806214145.02eacbb8@server-1.pragma-net.nl \
--to=pragma@wxs.nl \
--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).