From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: vertical alignment of table of contents in makeup
Date: Sat, 20 Dec 2014 23:41:23 +0100 [thread overview]
Message-ID: <5495FB13.8000409@gmx.es> (raw)
In-Reply-To: <CAE4-1rUL8TMPk4awsvq-q1B_+CY8PaXCBg0nhCFxkBhZksSSZQ@mail.gmail.com>
On 12/20/2014 03:13 AM, Mark Szepieniec wrote:
> There is a trick mentioned on the wiki for top-aligning the contents of
> a makeup page, namely adding "top=,", which cancels the default value of
> \vss, which is infinitely strechable space.
>
> However, that doesn't seem to work when the first element in the makeup
> page is \completecontent:
Hi Mark,
this is what it happens when you start a makeup page with a \chapter
command. \chapter inserts a page break before the heading.
> [...]
> Here, the table of contents and the section are both placed on the
> makeup page, but they are centered vertically. If the \completecontent
> line is commented out, the correct vertical alignment of the section
> header is obtained. Is there a way to get top-alignment when a makeup
> page starts with \completecontent? Is this a bug?
As far as I know, this isn’t a bug.
You can disable the page break before chapter with:
\setuphead[chapter][page=]
This way it works as you intend.
> Or should I even be using makeup pages in my table of contents?
I wonder whether this makes sense at all.
Why do you want or why do you think you need the table of contents
wrapped in a makeup page?
A makeup page is fine for contents such as title pages, colophons or
similar ones. Their contents should fit in a single page, because the
contents won’t be split across pages.
Here you have a sample that shows why makeup pages shouldn’t be used for
table of contents:
\starttext
\startmakeup[standard][top=,]
\chapter{Contents}
\dorecurse{50}{\section{testsection}}
\stopmakeup
\stoptext
I hope it helps,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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:[~2014-12-20 22:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-20 2:13 Mark Szepieniec
2014-12-20 22:41 ` Pablo Rodriguez [this message]
2014-12-21 20:01 ` Mark Szepieniec
2014-12-21 21:12 ` Pablo Rodriguez
2014-12-21 21:29 ` Mark Szepieniec
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=5495FB13.8000409@gmx.es \
--to=oinos@gmx.es \
--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).