From: Gilbert van den Dobbelsteen <GILBERT@login.iaf.nl>
Subject: Re: waarom zie ik geen inhoud?
Date: Wed, 23 Oct 2002 16:38:31 +0000 (UTC) [thread overview]
Message-ID: <363d8185.login@login.iaf.nl> (raw)
> De volgende source laat geen inhoudsopgave zien. Ik heb ook veel
> ge-experimenteerd met \definieerlijst en \definieersamengesteldelijst,
> maar nog nooit een inhoud gezien.
>
> Als ik ipv \plaatsinhoud \volledigeinhoud zet, dan verschijnt wel een
> kop "Inhoud", maar niets daarachter.
Aha, you should run context twice, and run texutil in between. The
contents is placed in \jobname.tui by TeX, texutil then generated
\jobname.tuo (tui-->TexUtil Input, tuo --> TexUtil Ouput).
Beware: if \jobname.tuo doesn't exist context generates a default one.
You can check the .tui/.tuo files and it should contain the section
headings.
If you use perl:
texexec \jobname
where \jobname is (of-course) the name of the .tex file you want to
process.
Please, please please use the texexec perl script. It solves many
beautiful things people tend to forget. texexec also makes sure the
correct number of tex-runs are made. In the beginning this is annoying,
because you think it runs tex one time to many, but if you look inside
the perl script you know it is doing the correct job.
TexExec also tries to guess the interface language, and
automagically uses cont-en or cont-nl.
Gilbert.
next reply other threads:[~2002-10-23 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 16:38 Gilbert van den Dobbelsteen [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-11-02 9:33 Hans Hagen
1998-11-01 19:55 W.H. Dekker
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=363d8185.login@login.iaf.nl \
--to=gilbert@login.iaf.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).