From: Willi Egger <w.egger@boede.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Table of Contents with unnumbered Chapters etc
Date: Wed, 8 Jul 2009 16:51:36 +0200 [thread overview]
Message-ID: <CC0886BA-E3B4-47E1-9526-7FB1F2D36742@boede.nl> (raw)
In-Reply-To: <4BB0C1EB-EB09-4449-A01D-2056AF9E6419@planet.nl>
Hi,
the subjects and susubjects will not end up in a TOC. Use section and
subsection. Add a \setuphead[section,subsection][number=no], place
the TOC with \completecontent.
Willi
On Jul 8, 2009, at 1:33 PM, Robert Blackstone wrote:
> Hi all,
> I am struggling, vainly so far, with "list" and "combinedlist", and
> I hope someone can help me.
> What I want to do is the following: I am making a bilingual version
> om some old German text, adding an English translation. As in the
> original German version, I want to use unnumbered chapters,
> sections etc. but I still do want a table of contents.
> I had the impression "unnumbered" can be achieved by using "title",
> "subject", etc instead of "chapter", "section", etc and still get a
> table of contents by means of a combined list. But whatever I
> tried, no list is ever placed anywhere and even
> \completecombinedlist[contents][level=subject] is seen as an
> undefined control sequence.
>
> I have used ConTeXt from TeXlive-2008 via TeXShop, and Minimals
> (ConTeXt ver: 2009.06.14 21:01 MKIV) via Terminal, but the result
> is the same.
>
> No doubt I do some things totally wrong but I can't help having a
> sneaking suspicion that something is wrong with "list"s.
>
> I have uploaded a small testfile, which can be downloaded from the
> following link: http://web.me.com/blackstone.robert/filechute/
> Wegweiser-testfile-a.tex
> (In this testfile there are lots of things I tried and subsequently
> commented out.)
> Thanks in advance.
>
> Robert
> Blackstone____________________________________________________________
> _______________________
> 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 : https://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ______________________________________________________________________
> _____________
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-07-08 14:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 11:33 Robert Blackstone
2009-07-08 14:31 ` Wolfgang Schuster
2009-07-08 14:51 ` Willi Egger [this message]
2009-07-09 8:12 Robert Blackstone
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=CC0886BA-E3B4-47E1-9526-7FB1F2D36742@boede.nl \
--to=w.egger@boede.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).