Changes

Jump to navigation Jump to search
905 bytes removed ,  19:36, 3 November 2021
m
<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 has a separate special layout, allowing for custom and temporary header & footer sections. Pages that need not rely on the current pagelayout style typically include covers, colophons, like a title page or colofonsimilar. There is one standard makeup page, but you can define more if needed.
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) rely on the current page layout style, which is especially useful for title pages.</pre>&mdash; Taco, in http://www.ntg.nl/pipermail/ntg-context/2010/049662.html== Examples ==
<pre>> Hi everyone, > > I cannot see any effect when using voffset and hoffset as There are a parameter for > \startstandardmakeup. For example: > > \startstandardmakeup[headerstate=none, footerstate=none, > hoffset=1in, hoffset=1in, width=4in, height=7.0in] > ... > \stopstandardmakeup > > I'd expect them few ways to shift the page content up and to the > right, respectively. This is guessing from their nameinvoke a custom makeup: I actually cannot find > any documentation on these parameters. Am I missing something?
indeed they are obsolete ... layers are better for that </pretexcode>&mdash; Hans, http://www\definemakeup[custom][align=middle]\starttext\startmakeup[custom]This is a title page.ntg.nl/pipermail/ntg-context/2010/051896.html\stopmakeup
=Introduction=\input zapfA makeup is an special kind of page that some documents might contain.\stoptextIt is intended for covers, colophons or similar pages. Their keyfeature is that they don’t have to rely on the current page layoutstyle.</texcode>
There is one standard makeup, but more can This may be defined when needed. The way easily extended to invoke them is one of the following twohaving multiple divider (title) pages:
<texcode>
\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 <cmd>setupmakeup</cmd>.And then extend to others:
<texcode>\definemakeup[customone][align=middle]\definemakeup[customtwo][bottom=,] % See note below on Vertical aligment of Alignment\starttext\startcustomonemakeupThis is a title/divider page using customone.\stopcustomonemakeup \input ward \startcustomtwomakeupThis is a title/divider page using customtwo.\stopcustomtwomakeup \input zapf\stoptext</texcode> By default, makeupslack both header and footers. They are vertically centered and horizontally aligned to the left.. == Vertical Aligment ==
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]]

Navigation menu