<pre>> 2) What \startstandardmakeup do then? And what is the purpose of defining custom makeups? From the source (and I am positive this is also mentioned in the big manual): == Description ==
A makeup is a separate single page, like with a title page or colofon. There is one standard makeup pagespecial layout, but you can define more if neededallowing for custom and temporary header and footer sections.
As can be seen in http://wiki.contextgarden.net/Command/setupmakeup it is a page type with a special layout / header & footer sections that last only temporarily. The key point is that such a page does not (have to) Makeups don’t rely on the current page layout style, which is especially useful for title pages.</pre>— Tacoand they typically include covers, in http://www.ntg.nl/pipermail/ntg-context/2010/049662colophons or similar ones.html
<pre>> Hi everyone, > > I cannot see In any effect when using voffset and hoffset as a parameter for > \startstandardmakeup. For example: > > \startstandardmakeup[headerstate=nonecase, footerstate=none, > hoffset=1in, hoffset=1in, width=4in, height=7.0in] > ... > \stopstandardmakeup > > I'd expect them it is important not to shift the page content up and to the > right, respectivelyforget that makeup contents will never split in pages. This is guessing from their name: I actually cannot find > any documentation All makeup contents must fit on these parametersa single page. Am I missing something?
indeed they There are obsolete ... layers are better for that predefined makeups: <code>standard</code>, <code>page</precode>— Hans, http:<code>text</code> and <code>middle</wwwcode>.ntg.nl/pipermail/ntg-context/2010/051896Of course, you can define as many as you may need.html
=Introduction=A makeup is an special kind of page that some documents might contain.It is intended for coversBy default, colophons or similar pages. Their keyfeature is that they don’t makeups have to rely on the current page layoutstyle.following properties:
There is one standard makeup# They aren’t numbered in the final document (<code>pagestate=start</code> changes this).# In double-sided documents, but more can be defined when neededthey are always on an odd page with the next page empty (<code>page=yes</code> and <code>doublesided=no</code> change each of these defaults).# They don’t include header or footers (use either <code>headerstate=start</code> or <code>footerstate=start</code> to change it).# They are left aligned (use the <code>align</code> option key [and {{cmd|dontleavehmode}} with {{cmd|externalfigure}}]).
The way All makeups have an associated layout. So you may use {{cmd|setuplayout}} to tweak it (besides configuring the makeup itself). == Examples == There are a few ways to invoke them is one of a custom makeup (and to compare it with the following twoother predefined makeups):
<texcode>
\showframe
\setuppagenumbering[alternative=doublesided, page=,]
\setupmakeup[pagestate=start]
\definemakeup[custom][align=middle]
\starttext
\startmakeup[custom]
This is a title page.
\stopmakeup
\startmakeup[text]
This is a title page.
\stopmakeup
\startmakeup[middle]
This is a title page.
\stopmakeup
\startmakeup[standard]
This is a title page.
\stopmakeup
\startmakeup[page]
This is a title page.
\stopmakeup
\input zapf
\stoptext
</texcode>
This may be easily extended to having multiple divider (title) pages:
<texcode>
\definemakeup[custom][align=middle]
\starttext
\startmakeup[custom]
This is a divider page.
\stopmakeup
\input tufte
\startmakeup[custom]
This is a second divider page.
\stopmakeup
\input ward
\startmakeup[custom]
This is a divider title page.
\stopmakeup
\stoptext
</texcode>
Another way to start a previously defined <code>makeup</code> is to put it into the <code>\start</code> invocation, i.e., \start<''name''>makeup</code>. In the above case we can simply refer to the ''custom'' <code>makeup</code> with <code>\startcustommakeup</code>:
<texcode>
\stoptext
</texcode>
By default, makeups lack both header and footers. They are vertically
centered and horizontally aligned to the left.
Configuration options can be found at And then extend to others: <cmdtexcode>setupmakeup<\definemakeup[customone][align=middle]\definemakeup[customtwo][bottom=,] % See note below on Vertical Alignment\starttext\startcustomonemakeupThis is a title/cmd>divider page using customone.\stopcustomonemakeup
\input ward \startcustomtwomakeupThis is a title/divider page using customtwo.\stopcustomtwomakeup \input zapf\stoptext</texcode> By default, makeups lack both header and footers. They are vertically centered and horizontally aligned to the left.. ==Vertical aligment of makeupsAligment ==
Makeups are centered vertically by default.
</texcode>
== Horizontal Aligment == Horizontal aligment is specified with the <code>align</code> optionas in: <texcode>\definemakeup[custom][align=flushright] % align here is used to set text flush to the right\starttext\startcustommakeupThis is a title page.\stopcustommakeup \input zapf\stoptext</texcode> == See Also == * {{cmd|setupmakeup}}* http://wiki.contextgarden.net/Command/setupmakeup* http://www.ntg.nl/pipermail/ntg-context/2010/049662.html* http://www.ntg.nl/pipermail/ntg-context/2010/051896.html [[Category:Basics]][[Category:Layout]]