headers and footers

newer
Strange font issue with LuaTeX on...

older
Re: [NTG-context] Is there some...

Alan Stone

28 Aug 2008 28 Aug '08

7:18 p.m.

Hi, Main manual pg 78, § 4.17: \setup*texts *[.1.]* [.2.] [.3.] commands "When the first argument is left out it is taken for granted that the footer and header should be place under or over the pagebody (text)." What does this mean ? Thanks, Alan

Attachments:

attachment.html (text/html — 429 bytes)

Show replies by date

Wolfgang Schuster

29 Aug 29 Aug

8:33 a.m.

On Thu, Aug 28, 2008 at 7:18 PM, Alan Stone wrote:

...

Hi,

Main manual pg 78, § 4.17: \setup*texts [.1.] [.2.] [.3.] commands

"When the first argument is left out it is taken for granted that the footer and header should be place under or over the pagebody (text)."

What does this mean ?

\setupheadertexts[...][...] is equal to \setupheadertexts[text][...][...] and place the header texts above the normal text area. \setupheadertexts[margin][...][...] place the header texts in the left and the right margin. Wolfgang

Jano Kula

9:57 a.m.

Hi, Alan Stone wrote:

...

Hi,

Main manual pg 78, § 4.17: \setup*texts /[.1.]/ [.2.] [.3.] commands

"When the first argument is left out it is taken for granted that the footer and header should be place under or over the pagebody (text)."

What does this mean ?

First (optional) parameter defaults to "text" (positioning over/under "text" area). This parameter says over/under which page area headers/footers are placed. One could choose "margin" or "edge" areas also. Jano

Alan Stone

10:53 a.m.

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 ? Best, Alan

Taco Hoekwater

12:21 p.m.

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). Best wishes, Taco

Yue Wang

12:38 p.m.

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 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).

Best wishes, Taco ___________________________________________________________________________________ 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 ___________________________________________________________________________________

Wolfgang Schuster

1:20 p.m.

On Fri, Aug 29, 2008 at 12:38 PM, Yue Wang 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 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

Yue Wang

1:43 p.m.

No. The example and the code do not match. should be corrected. On Fri, Aug 29, 2008 at 7:20 PM, Wolfgang Schuster wrote:

...

On Fri, Aug 29, 2008 at 12:38 PM, Yue Wang 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 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 ___________________________________________________________________________________

Taco Hoekwater

2:23 p.m.

Yue Wang wrote:

...

No. The example and the code do not match. should be corrected.

I see it too. Almost as if Figure 3.3 and 3.4 are copies of 3.2. Best wishes, Taco

Alan Stone

5:06 p.m.

(1) The main manual mentions (bottom of pg 78) "setting the state is done for the whole header" and (bottom of page 79) "the keys state, before and after work on all parts of the pagebody, main text, margins and edges. So there's no way to set the text/margin/edge states separately ? ( I need different visible/invisible settings for standard, frontapart and backpart ) (2) pg 80 table 4.5: what's the difference between state=normal and state=start ? (3) in \setup*[margin/edge] ( * = top/header/footer/bottom ), how do you differentiate between the left and right margin/edge areas ? Thanks and have a great weekend, Alan

Alan Stone

1 Sep 1 Sep

3:31 p.m.

I'm asking questions (1) and (3) since the main manual was written in 2001. Best, Alan On Fri, Aug 29, 2008 at 5:06 PM, Alan Stone wrote:

...

(1) The main manual mentions (bottom of pg 78) "setting the state is done for the whole header" and (bottom of page 79) "the keys state, before and after work on all parts of the pagebody, main text, margins and edges.

So there's no way to set the text/margin/edge states separately ? ( I need different visible/invisible settings for standard, frontapart and backpart )

(2) pg 80 table 4.5: what's the difference between state=normal and state=start ?

(3) in \setup*[margin/edge] ( * = top/header/footer/bottom ), how do you differentiate between the left and right margin/edge areas ?

Thanks and have a great weekend, Alan

6121

Age (days ago)

6125

Last active (days ago)

List overview

Download

10 comments

5 participants

participants (5)

Alan Stone
Jano Kula
Taco Hoekwater
Wolfgang Schuster
Yue Wang