ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm <hraban@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: headers and pagenumbering
Date: Sat, 3 May 2008 21:29:03 +0200	[thread overview]
Message-ID: <46DDD225-66D9-461A-A856-5E0C32FA4674@fiee.net> (raw)
In-Reply-To: <20080503075441.1f055b9f.schuster.wolfgang@googlemail.com>

Am 2008-05-03 um 07:54 schrieb Wolfgang Schuster:
>> (1) % or 0? ;-)
>> I struggled how to leave out the pagina on the ToC page, no setups
>> seemed to work.
>> I just reckognized that I need the \page inside of the braced area.
>
> I will use a simple example ti explain where you need to insert a
> pagebreak to get the desired output.

Yes, I got it now, hoepfully, thank you!

!!
> \setupheader disables it only on the current page, it is a local  
> value.
!!

I didn't understand how \setupheader works - now it's clear that  
\setupheader[chapter] affects only the first page of the chapter and  
\setupheader[text] affects the rest.

But if I add "header=high" to my \setupheader[chapter], my last  
component=chapter in bodymatter (only one page) breaks with:

----%%%----
systems         : end file c_14_kirchen at line 54
structure       : end of sectionblock bodymatter
! Missing \endcsname inserted.
<to be read again>
                    \currentsectionworldname
<argument> \??ko \currentsectionworldname
                                           \c!header
\getvalue #1->\csname #1
                         \endcsname
\doifelselayoutsomeline ... #1\c!state \endcsname
                                                   }\ifx \!!stringa  
\v!none \...

\calculatereducedvsizes ...youtsomeline \v!header
                                                   {\advance  
\textheight -\di...

\gettextboxes ...complain \calculatereducedvsizes
                                                   \swapmargins  
\offinterline...
...
l.56 \stopbodymatter
----%%%----

If I comment out this last component or move it in front of the  
second-last, everything is well. The file itself contains no errors  
(at least I couldn't find any).
Don't know how to get a failing minimal for such a problem...



Greetlings from Lake Constance!
Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)

___________________________________________________________________________________
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
___________________________________________________________________________________


      reply	other threads:[~2008-05-03 19:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30 15:28 Henning Hraban Ramm
2008-05-03  5:54 ` Wolfgang Schuster
2008-05-03 19:29   ` Henning Hraban Ramm [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=46DDD225-66D9-461A-A856-5E0C32FA4674@fiee.net \
    --to=hraban@fiee.net \
    --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).