From: Mark Szepieniec <mszepien@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: setting margins in makeup
Date: Sun, 21 Dec 2014 21:03:46 +0100 [thread overview]
Message-ID: <CAE4-1rU2RxGQNOv8f+bWdrv3LbE4SPwwa5gcjNXuKcU-mh-Sng@mail.gmail.com> (raw)
In-Reply-To: <5496A8AA.7070103@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 2243 bytes --]
On Sun, Dec 21, 2014 at 12:02 PM, Hans Hagen <pragma@wxs.nl> wrote:
>
> On 12/20/2014 11:55 PM, Pablo Rodriguez wrote:
>
>> On 12/19/2014 04:38 PM, Mark Szepieniec wrote:
>>
>>> [...]
>>> Incidentally, what threw me off was the phrasing in the manual:
>>>
>>> 4.19
>>> Makeup
>>> A document may have a titlepage, a colofon and some pages that are
>>> not directly related to the main part of the document. Mostly these
>>> pages are not numbered and can do without headers and footers.
>>> Because their layout needs extra attention we prefer the word makeup
>>> for defining their specific layout.
>>>
>>> Since my makeup pages indeed don't have page numbers, I presumed they
>>> wouldn't have headers either. I may have read too much into that, but
>>> perhaps that passage can be improved?
>>>
>>
>> Hi Mark,
>>
>> makeups don’t have either headers or footers, but have the document
>> layout unless otherwise specified.
>>
>> You are right: makeups don’t have header or footer /texts/, although
>> they don’t have the space for headers and footers removed.
>>
>
> they have them but their state is empty (headerstate etc parameters)
>
> Hans
>
Thanks for the clarification both of you, that was exactly what I was
getting wrong.
Best,
Mark
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
> | www.pragma-pod.nl
> -----------------------------------------------------------------
>
> ____________________________________________________________
> _______________________
> 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
> ____________________________________________________________
> _______________________
>
[-- Attachment #1.2: Type: text/html, Size: 3645 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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-21 20:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 14:33 Mark Szepieniec
2014-12-19 15:38 ` Mark Szepieniec
2014-12-20 22:55 ` Pablo Rodriguez
2014-12-21 11:02 ` Hans Hagen
2014-12-21 20:03 ` Mark Szepieniec [this message]
2014-12-20 22:51 ` Pablo Rodriguez
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=CAE4-1rU2RxGQNOv8f+bWdrv3LbE4SPwwa5gcjNXuKcU-mh-Sng@mail.gmail.com \
--to=mszepien@gmail.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).