ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Wolfgang Schuster" <schuster.wolfgang@googlemail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: headers and footers
Date: Fri, 29 Aug 2008 13:20:47 +0200	[thread overview]
Message-ID: <115224fb0808290420w6f253475if0419abc39d2bd3e@mail.gmail.com> (raw)
In-Reply-To: <68bfdc900808290338p11e59c03qd6a311892f806517@mail.gmail.com>

On Fri, Aug 29, 2008 at 12:38 PM, Yue Wang <yuleopen@gmail.com> wrote:
> OK, today I read the chapter again and I am sure examples in pages
> like pp36, pp37 of cont-eni.pdf are wrong.
> Zoom your Adobe Reader to 600% and notice the header text.
>
> On Fri, Aug 29, 2008 at 6:21 PM, Taco Hoekwater <taco@elvenkind.com> wrote:
>> Alan Stone wrote:
>>> Ok thanks.
>>>
>>> Next, pg 80 table 4.5, result column
>>>
>>> state       result
>>> ----------------------------------------------------------
>>> none       invisible, no whitespace
>>> empty     one page invisible, whitespace
>>> high        one page visible, no whitespace
>>> stop        invisible, whitespace
>>>
>>> What does this mean ?
>>
>> The first column describes with the content will be visible or not.
>> The "one page" ones revert to the 'normal' behaviour after one page
>> (this is useful for e.g. chapter title pages).
>>
>> The second column controls whether the header/footer gets any space
>> allocated for its content (on title pages, you may want to use the
>> full height, including the space that is normally reserved for the
>> headers/footers).

You mean \setupheadertexts[..][..][..][..].

This was already mentioned a few days ago, it's front side/back side and
not left page/right page.

Wolfgang
___________________________________________________________________________________
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-08-29 11:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-28 17:18 Alan Stone
2008-08-29  6:33 ` Wolfgang Schuster
2008-08-29  7:57 ` Jano Kula
2008-08-29  8:53   ` Alan Stone
2008-08-29 10:21     ` Taco Hoekwater
2008-08-29 10:38       ` Yue Wang
2008-08-29 11:20         ` Wolfgang Schuster [this message]
2008-08-29 11:43           ` Yue Wang
2008-08-29 12:23             ` Taco Hoekwater
2008-08-29 15:06               ` Alan Stone
2008-09-01 13:31                 ` Alan Stone
  -- strict thread matches above, loose matches on Subject: below --
2000-10-22 23:27 Headers " Giuseppe Bilotta
2000-10-24  7:09 ` Hans Hagen
2000-05-16 21:14 headers " Hraban
2000-05-17 15:29 ` Hans Hagen
1999-08-22  7:45 Headers " David Arnold
1999-08-22 12:42 ` Tobias Burnus
1999-08-22 20:01   ` Hans Hagen
1999-08-23  8:09     ` Tobias Burnus
1999-08-24 23:28     ` David Arnold
1999-08-25  7:35 ` Hans Hagen

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=115224fb0808290420w6f253475if0419abc39d2bd3e@mail.gmail.com \
    --to=schuster.wolfgang@googlemail.com \
    --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).