From: Steffen Wolfrum <context@st.estfiles.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Is it possible to generate only a table of contents
Date: Fri, 18 Mar 2011 10:09:11 +0100 [thread overview]
Message-ID: <B06920D9-369C-4630-A7EB-86F784F3DE2E@st.estfiles.de> (raw)
In-Reply-To: <AANLkTinBpo5QRbWRM=oJCyN07Yhxw8_Gbzxg9rxnLFWz@mail.gmail.com>
Am 18.03.2011 um 09:32 schrieb Cecil Westerhof:
> Is it possible to generate only a TOC? (\completecontent) When creating a document I like to have the 'stakeholders' to have an indication of what is going on. For this a TOC is enough. I could create the document and cut out the TOC, but it would be simpler if that could be auto generated.
In MkII this was possible by accessing the TUO file (which contains the TOC entry information) directly and independently .
When typesetting a document "MyFile.tex" there is an accompanied TUO file generated "MyFile.tuo".
Just copy this file and re-name to eg. MyFileX.tuo
Then you can run \placelist[chapter, section,...][file=MyFile] from any document that contain these line:
\unprotect
\def\FrozenTUO{../MyFileX}
\def\doplacerawlist[#1][#2]%
{\begingroup
\dogetcommalistelement1\from#1\to\firstlistelement
\dosetuplist[#1][#2]%
\doifvalue{\??li\firstlistelement\c!coupling}\v!on
{\startlistreferences{#1}}%
\dosettoclevel\??li\firstlistelement
\honorlocalfilterlevel
\doutilities{listentries,#1}\FrozenTUO{#1}\relax\par
\stoplistreferences{#1}%
\dosetlistmode
\endgroup}
\protect
In MkIV this is not possible up to now due to the completely different structure of TOU and TUC files (see Hans below) ... unfortunately.
Steffen
Am 23.02.2010 um 23:27 schrieb Hans Hagen:
> On 23-2-2010 21:18, Steffen Wolfrum wrote:
>>
>> \def\FrozenTUO{MyFile}
>>
>> .... thus each \placelist run would read from that paticular MyFile.tuo
>>
>> The quoted code above was written by Hans to provide a way to implement a kind of \placelist[chapter, section,...][file=MyFile] in MkII.
>
> the file= option will not come back, at least not soon, as we now have a completely different way of dealing with tables of contents (and actually all multipass data)
___________________________________________________________________________________
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-03-18 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 8:32 Cecil Westerhof
2011-03-18 9:09 ` Steffen Wolfrum [this message]
2011-03-18 9:35 ` Peter Münster
2011-03-18 11:19 ` luigi scarso
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=B06920D9-369C-4630-A7EB-86F784F3DE2E@st.estfiles.de \
--to=context@st.estfiles.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).