TeX/LaTeX: an open-source typesetting system for text, mathematical formulas and much more.

Fixed-width horizontal space*

Fixed-length vertical space*

Variable-size space*

Constructing hboxes and vboxes

\hbox {<horizontal mode material>}
\hbox to <dimen {<horizontal mode material}
    \hbox spread <dimen {<horizontal mode material>}

This command produces an hbox (horizontal box) containing <horizontal mode materiali>. The braces around <horizontal mode material> define a group. TEX doesn't break the <horizontal mode material> into lines, since it's in restricted horizontal mode when it's assembling the box. TEX won't change the size of the box once it's been produced.

\hbox is often useful when you want to keep some text all on one line. If your use of \hbox prevents TEX from breaking lines in an acceptable way, TEX will complain about an overfull hbox.

The width of the hbox depends on the arguments to \hbox:

If you specify only <horizontal mode material>, the hbox will have its natural width.
If you specify to <dimen>, the width of the hbox will be <dimen
If you specify spread <dimen>, the width of the hbox will be its natural width plus <dimen>, i.e., the hbox will be spread out by <dimen>.

Example:

\hbox{ugly suburban sprawl}
\hbox to 2in{ugly \hfil suburban \hfil sprawl}
\hbox spread 1in {ugly \hfil suburban \hfil sprawl}
% Without \hfil in the two preceding lines,
% you’d get ‘underfull hbox’es.

For holding vertical mode material:

\vtop vertical mode material
\vtop to hdimeni { vertical mode material }
\vtop spread hdimeni { vertical mode material }
\vbox { vertical mode material }
\vbox to hdimeni { vertical mode material }
\vbox spread hdimeni { vertical mode material }

These commands produce a vbox (vertical box) containing vertical mode material. The braces around vertical mode material define a group. TEX is in internal vertical mode when it's assembling the box. TEX won't change the size of the box once it's been produced.

The difference between \vtop and \vbox lies in where TEX puts the reference point of the constructed vbox. Ordinarily, the reference point gotten from \vtop tends to be at or near the top of the constructed vbox, while the reference point gotten from \vbox tends to be at or near the bottom of the constructed vbox. Thus a row of vboxes all constructed with \vtop will tend to have their tops nearly in a line, while a row of vboxes all constructed with \vbox will tend to have their bottoms nearly in a line.

\vtop and \vbox are often useful when you want to keep some text together on a single page. (For this purpose, it usually doesn't matter which command you use.) If your use of these commands prevents TEX from breaking pages in an acceptable way, TEX will complain that it's found an overfull or underfull vbox while \output is active.

The height of a vbox depends on the arguments to \vtop or \vbox. For \vbox, TEX determines the height as follows:

If you specify only vertical mode material, the vbox will have its natural height.
If you specify to dimen, the height of the vbox will be dimen.
If you specify spread dimen, the height of the vbox will be its natural height plus dimen, i.e., the height of the vbox will be stretched vertically by dimen.

For \vtop, TEX constructs the box using its rules for \vbox and then apportions the vertical extent between the height and the depth as described below.

Ordinarily, the width of a constructed vbox is the width of the widest item inside it. (More precisely, it's the distance from the reference point to the rightmost edge of the constructed vbox. Therefore, if you move any of the items right using \moveright or \moveleft (with a negative distance), the constructed vbox might be wider.) The rules for apportioning the vertical extent between the height and the depth are more complicated:

For \vtop, the height is the height of its first item, if that item is a box or rule. Otherwise the height is zero. The depth is whatever vertical extent remains after the height is subtracted.
For \vbox, the depth is the depth of its last item, if that item is a box or rule. Otherwise the depth is zero. The height is whatever vertical extent remains after the depth is subtracted. (In fact, there's a further complication. Suppose that after the depth has been determined using the two rules just given, the depth turns out to be greater than \boxmaxdepth. Then the depth is reduced to \boxmaxdepth and the height is adjusted accordingly.)

The \vfil command is useful for filling out a vbox with empty space when the material in the box isn't as tall as the vertical extent of the box.

Example:

\hbox{\hsize = 10pc \raggedright\parindent = 1em
\vtop{In this example, we see how to use vboxes to
produce the effect of double columns. Each vbox
contains two paragraphs, typeset according to \TeX’s
usual rules except that it’s ragged right.\par
This isn’t really the best way to get true double
columns because the columns}
\hskip 2pc
\vtop{\noindent
aren’t balanced and we haven’t done anything to choose
the column break automatically or even to fix up the
last line of the first column.\par
However, the technique of putting running text into a
vbox is very useful for placing that text where you
want it on the page.}}

Another example:

\hbox{\hsize = 1in \raggedright\parindent = 0pt
\vtop to .75in{\hrule This box is .75in deep. \vfil\hrule}
\qquad
\vtop{\hrule This box is at its natural depth. \vfil\hrule}
\qquad
\vtop spread .2in{\hrule This box is .2in deeper than
                        its natural depth.\vfil\hrule}}

Yet another example:

% See how \vbox lines up boxes at their bottoms
% instead of at their tops.
\hbox{\hsize = 1in \raggedright
\vbox to .5in{\hrule This box is .5in deep.\vfil\hrule}
\qquad
\vbox to .75in{\hrule This box is .75in deep.\vfil\hrule}}

\boxmaxdepth [ <dimen> parameter ]

This parameter contains a dimension D. TEX will not construct a box whose depth exceeds D. If you produce a box whose depth d would exceed D, TEX will transfer the excess depth to the height of the box, effectively moving the reference point of the box down by d − D. If you set \boxmaxdepth to zero, TEX will line up a row of vboxes so that their bottom boundaries all lie on the same horizontal line. Plain TEX sets \boxmaxdepth to \maxdimen, so \boxmaxdepth won't affect your boxes unless you change it.

\underbar [ <argument>]

This command puts argument into an hbox and underlines it without regard to anything that protrudes below the baseline of the box.

Example:

\underbar{Why not learn \TeX?}

Setting and retrieving the contents of boxes*

Shifting boxes

Use:

\moveleft dimen box
\moveright dimen box

These commands move box left or right by dimen (which can be neg- ative). You can only apply \moveleft and \moveright to a box that's in a vertical list.

Example:

\vbox{\vbox{Phoebe}\vbox{walked}%
\moveleft 20pt\vbox{a}\moveright 20pt\vbox{crooked}%
\vbox{mile.}}

\lower dimen box
\raise dimen box

These commands move box up or down by dimen (which can be negative). You can only apply \raise and \lower to a box that's in a horizontal list.

Another example:

Are you feeling \lower 6pt \hbox{depressed} about the
                \raise 6pt \hbox{bump} on your nose?

Dimensions of box registers

\ht register
\dp register
\wd register
[ dimen parameter ]
[ dimen parameter ]
[ dimen parameter ]

These parameters refer to the height, depth, and width respectively of box register register. You can use them to find out the dimensions of a box. You can also change the dimensions of a box, but it's a tricky business; if you want to be adventurous you can learn all about it from pages 388–389 of The TEXbook.

Example:

\setbox0 = \vtop{\hbox{a}\hbox{beige}\hbox{bunny}}
The box has width \the\wd0, height \the\ht0, and depth \the\dp0.

produces

The box has width 27.2223pt, height 4.30554pt, and depth 25.94444pt.

Struts, phantoms, and empty boxes

\strut

This command produces a box whose width is zero and whose height (8.5pt) and depth (3.5pt) are those of a more or less typical line of type in cmr10, the default plain TEX font. Its main use is in forcing lines to have the same height when you've disabled TEX's interline glue with \offinterlineskip or a similar command, e.g., when you're constructing an alignment. If the natural height of a line is too short, you can bring it up to standard by including a \strut in the line. The strut will force the height and depth of the line to be larger, but it won't print anything or consume any horizontal space.

If you're setting type in a font that's bigger or smaller than cmr10, you should redefine \strut for that context.

Example:

\noindent % So we're in horizontal mode.
\offinterlineskip % So we get the inherent spacing.
% The periods in this vbox are not vertically equidistant.
\vtop{\hbox{.}\hbox{.(}\hbox{.x}
  \hbox{.\vrule height 4pt depth 0pt}}\qquad
% The periods in this vbox are vertically equidistant
% because of the struts.
\vtop{\hbox{.\strut}\hbox{.(\strut}\hbox{.x\strut}
  \hbox{.\vrule height 4pt depth 0pt\strut}}

\mathstrut

This command produces a phantom formula whose width is zero and whose height and depth are the same as those of a left parenthesis. \mathstrut is in fact defined as \vphantom(. Its main use is for getting radicals, underbars, and overbars to line up with other radicals, underbars, and overbars in a formula. It is much like \strut, except that it adjusts itself to the different styles that can occur in math formulas.

Example:

$$\displaylines{
\overline{a_1a_2} \land \overline{b_1b_2}
\quad{\rm versus}\quad \overline{a_1a_2\mathstrut}
  \land \overline{b_1b_2\mathstrut}\cr
\sqrt{\epsilon} + \sqrt{\xi} \quad{\rm versus}\quad
\sqrt{\epsilon\mathstrut} + \sqrt{\xi\mathstrut}\cr}$$

\phantom argument

This command produces an empty box having the same size and placement that argument would have were it typeset. One use of \phantom is for reserving space for a symbol that for some reason needs to be drawn in by hand.

Example:

$1\phantom{9}2$

produces:

\hphantom argument
\vphantom argument

These commands produce phantom boxes that don't print anything:

\hphantom produces a box with the same width as argument but zero height and depth.
\vphantom produces a box with the same height and depth as argument but zero width.

Their main purpose is to force a subformula to have a certain minimum horizontal or vertical dimension.

Example:

$$\left[\vphantom{u\over v}t\right] \star
\left[{u\over v}\right]\quad
\{\hphantom{xx}\}$$

\smash argument

This command typesets argument, but forces the height and depth of its containing box to be zero. You can use \smash and \vphantom in combination to give a subformula any height and depth that you wish.

Example:

$${\smash{r_m \brace r_n}\vphantom{r}} \Longrightarrow r$$

\null

This command produces an empty hbox.

Example:

\setbox0 = \null
The null box \null has width \the\wd0, height \the\ht0,
and depth \the\dp0.

which produces:

The null box has width 0.0pt, height 0.0pt, and depth 0.0pt.

Parameters pertaining to malformed boxes*

Rules and leaders

If you don't specify the width of a vertical rule, it defaults to 0.4pt. If you don't specify the height or the depth of a vertical rule, the rule is extended to the boundary of the innermost box or alignment that contains the rule.

TEX treats a horizontal rule as an inherently vertical item and a vertical rule as an inherently horizontal item. Thus a horizontal rule is legal only in a vertical mode, while a vertical rule is legal only in a horizontal mode. If this seems surprising, visualize it—a horizontal rule runs from left to right and separates vertical items in a sequence, while a vertical rule runs up and down and separates horizontal items in a sequence.

Example:

\hrule\smallskip
\hrule width 2in \smallskip
\hrule width 3in height 2pt \smallskip
\hrule width 3in depth 2pt

Example:

% Here you can see how the baseline relates to the
% height and depth of an \hrule.
\leftline{
  \vbox{\hrule width .6in height 5pt depth 0pt}
  \vbox{\hrule width .6in height 0pt depth 8pt}
  \vbox{\hrule width .6in height 5pt depth 8pt}
  \vbox{\hbox{ baseline}\kern 3pt \hrule width .6in}
}

Example:

\hbox{( {\vrule} {\vrule width 8pt} )}
\hbox {( {\vrule height 13pt depth 0pt}
  {\vrule height 13pt depth 7pt} x)}
% the parentheses define the height and depth of each of the
% two preceding boxes; the ‘x’ sits on the baseline

\leaders box or rule skip command
\cleaders box or rule skip command
\xleaders box or rule skip command

These commands produce leaders, i.e., they fill a horizontal or vertical space with copies of a pattern. The box or rule specifies a leader, i.e., a single copy of the pattern, while the skip command specifies a window to be filled with a row or a column of the leaders. The pattern is repeated as many times as will fit into the window. If skip command is a horizontal skip, the window contains a row of leaders and TEX must be in a horizontal mode; if skip command is a vertical skip, the window contains a column of leaders and TEX must be in a vertical mode.

The commands differ in how they arrange the repeated pattern in the space and where they put any leftover space:

For \leaders, TEX aligns a row of leaders with the left end of the innermost box B that is to contain the result of the \leaders command. It aligns a column of leaders with the top of B. Those leaders that fall entirely within the window are retained. Any leftover space at the top and bottom of the window is left empty.
For \cleaders, the leaders are centered within the window.
For \xleaders the pattern is uniformly distributed throughout the window. If the leftover space is l and the leader is repeated n times, TEX puts space of width or height l/(n + 1) between adjacent leaders and at the two ends (left and right or top and bottom) of the leaders.

Example:

\def\pattern{\hbox to 15pt{\hfil.\hfil}}
\line{Down the Rabbit-Hole {\leaders\pattern\hfil} 1}
\line{The Pool of Tears {\leaders\pattern\hfil} 9}
\line{A Caucus-Race and a Long Tale {\cleaders\pattern\hfil} 19}
\line{Pig and Pepper {\xleaders\pattern\hfil} 27}

Another example:

\def\bulletfill{\vbox to 3ex{\vfil\hbox{$\bullet$}\vfil}}%
\def\mybox{\vbox to 1in}
\def\myrule{\hrule width 4pt}\hsize=2in
\hrule \line{%
  \mybox{\myrule depth 8pt \leaders\bulletfill\vfill}
  \hfil
  \mybox{\myrule depth 15pt \leaders\bulletfill\vfill}
  \hfil
  \mybox{\myrule depth 18pt \cleaders\bulletfill\vfill}
  \hfil
  \mybox{\myrule depth 12pt \xleaders\bulletfill\vfill}%
}\hrule

Tabbing alignments*

General alignments*

Greek letters for variables*

Accents in math mode

Mathematical accents are somewhat different, because spacing is not the same; TeX uses special conventions for accents in formulas, so that the two sorts of accents will not be confused with each other. The following math accents are provided by plain TeX and are exemplified atop letter 'a':

$\hat a$
$\check a$
$\tilde a$
$\acute a$
$\grave a$
$\dot a$
$\ddot a$
$\breve a$
$\bar a$
$\vec a$

The first nine of these are called \^, \v, \~, \', \`, \., \" , \u, and \=, respectively, when they appear in text; \vec is an accent that appears only in formulas. \TeX\ will complain if you try to use \^ or \v, etc., in formulas, or if you try to use \hat or \check, etc., in ordinary text.

When the letters i and j are accented in math formulas, dotless symbols \imath and \jmath should be used as provided in plain TeX.

Fractions, binomials, and limits

Fractions are made by typing \over between numerator and denominator. Binomials are made by typing \choose between its terms. Subscripts and superscripts of summations are printed over and under the summation sign in display mode. Try these:

$$n+1\over n+2$$
$${x+y^2\over k}+1$$
$$n+1\choose3$$
$$\sum_{n=1}^3 Z_n^2$$

Notice the second expression: sometimes grouping is necessary.

If the numerator of a fraction is a fraction, it should be set as with a slash: $${a \over b} \over 2$$

An expression over another expression

TeX has another operation \atop, which is like \over except that it leaves out the fraction line, as in $$x \atop y + 2$$. (\choose, for typing binomials, is a plain TeX macro based on \atop.)

Summations and Integrals

These are set through \sum and \int, with limits specified as subscripts and superscripts. In display mode they are printed larger, with limits over and under, whereas in text mode they are printed smaller with limits to the right, so as not to make too tall a box.

If you want the limits to be printed differently, you can type \limits or \nolimits right after the the large operator. For instance:

$$\int\limits_0^{\pi\over2}$$
$$\sum\nolimits_{n=1}^m$$

Lines under and over

TeX and Plain TeX provide four operators that span a group horizontally: \underline, \overline, \widehat and \widetilde. These are so straightforward to use that I will only provide two examples: $\underline 3$ and $\overline{\alpha^2}$.

Papersize

The format of the papersize special is \special{papersize=width,height}, where width is the horizontal size of the page, and height is the vertical size. The dimensions supported are the same as for TEX; namely, in (inches), cm (centimeters), mm (millimeters), pt (points), sp (scaled points), bp (big points, the same as the default PostScript unit), pc (picas), dd (didot points), and cc (ciceros).

You specify landscape orientation through \special{landscape}.

Including Encapsulated PostScript files

Scaling and including PostScript graphics is easy if the PostScript file is correctly formed, i.e. it includes an accurate bounding box comment, on the pattern %%BoundingBox: llx lly urx ury, such as:

%%BoundingBox: 0 0 150 100

Further, the first should start with the two magic characters %!.

Next, if you are using plain TEX, you need epsf.tex, therefore bring it in through a line \input epsf.

Last, at the point you want to include a file, enter a line such as \epsffile{<filename>.eps}. If you are in the middle of a paragraph, the EPS figure will be incorporated as a box in the current line, which will cause the common baseline to drop if the height of the figure is greater than the baselineskip. The origin of the figure will be the same as that of a character that were to be printed instead.

Here is a simple EPS file to test inside a tex file:

%!PS-Adobe-2.0 EPSF-2.0
%%BoundingBox: 0 0 100 19
/Times-Roman 22 selectfont

0 0 moveto
(Hello EPS!) show

(If your file does not have a bounding box comment, you can supply the numbers as determined in the previous section, in the same order they would have been in a normal bounding box comment: \epsffile[0 0 100 19]{hello.eps}.)

The \epsffile macro typesets the figure as a TEX \vbox at the point of the page that the command is executed. By default, the graphic will have its natural width (namely, the width of its bounding box). The TEX box will have depth zero and its natural height. By default, the graphic will be scaled by any DVI magnification in effect, just as is everything else in your document.

EPSF scaling

Usually, you will want to scale an EPSF figure to some size appropriate for your document, since its natural size is determined by the creator of the EPS file. The best way to do this is to assign the desired size to the TEX \epsfxsize or \epsfysize variables, whichever is more convenient for you. That is, put \epsfxsize=<dimen> right before the call to \epsffile. Then the width of the TEX box will be dimen and its height will be scaled proportionately. Similarly, you can set the vertical size with \epsfysize=<dimen> in which case the height will be set and the width scaled proportionally. And if you set both, both will be honored, but the aspect ratio of the included graphic may necessarily be distorted, i.e., its contents stretched in one direction or the other.

EPSF clipping

By default, clipping is disabled for included EPSF images. This is because clipping to the bounding box dimensions often cuts off a small portion of the figure, due to slightly inaccurate bounding box arguments. The problem might be subtle; lines around the boundary of the image might be half their intended width, or the tops or bottoms of some text annotations might be sliced off. If you want to turn clipping on, just use the command \epsfclipon and to turn clipping back off, use \epsfclipoff.

An example including EPS with graphics and text printed in a scaled inherited font:

\input epsf

%Hello \TeX !
% \epsfbox{square.eps} % include EPS file in horizontal mode, i.e. after the text, not below.

\hbox
{
  \epsfxsize=25pt \epsfbox{square.eps} % include EPS file in vertical mode
  \vbox {
    \noindent The four numbers in square brackets tell \TeX to use only part of the size of the graphic. In this example, \TeX would pretend that only the rectangle from (10,30) to (150,80) is actually used. The dimensions are points, so the graphic would have an effective size (for TeX's purposes) of (150-10) or 140 points wide by (80-30) or 50 points tall.
  }
}

\noindent The graphic is not actually cropped to the given size, it is only shifted on the page so that the lower left corner of the bounding box coincides with the lower left corner of the area \TeX reserves for it. In the example above, location (10,30) in the figure would be located at the lower left corner of the box in which TeX places the figure, but any part of the image outside the rectangle from (10,30) to (150,80) would still appear on the page.

\hbox {

  Bye \TeX !
  \special{ps: 200 200 moveto 500 dup rlineto 0.33 0.33 0 setrgbcolor 10 setlinewidth stroke}

  % What about...?
  \special{ps: gsave
                 currentfont 2 scalefont setfont
                 900 dup 2 mul moveto
                 0.2 setgray
                 (Test: currentfont 2 scalefont setfont) show grestore}

  %\epsfbox{square.eps} % include EPS file BELOW the text, not below.

  \vtop { \epsfxsize=10pt \epsfbox{square.eps} \epsfxsize=12pt \epsfbox{square.eps} \epsfxsize=33pt \epsfbox{square.eps}}

}

\bye

Including PostScript files

The basic special for file inclusion is as follows:

\special{psfile=<filename>.ps [<key>=<value>] ... }

This brings in the PostScript file <filename>.ps such that the current point will be the origin of the PostScript coordinate system. The optional key=value assignments allow you to specify transformations on the PostScript. The possible keys are:

hoffset: The horizontal offset (default 0). voffset: The vertical offset (default 0). hsize: The horizontal clipping size (default 612). vsize: The vertical clipping size (default 792). hscale: The horizontal scaling factor, as a percentage (default 100). vscale: The vertical scaling factor, as a percentage (default 100). angle: The rotation, in degrees (default 0). clip: Enable clipping to the bounding box (default disabled). llx, lly, urx, ury: Bounding box of the included image, just as in a %%BoundingBox comment. Values are in big points, and may be fractional. rhi, rwi: Desired width and height of the resulting figure in the output, in tenths of big points (720 to the inch); may be fractional. If both rwi and rhi are nonzero, the picture is scaled, possibly losing aspect ratio. If only one of rwi and rhi is nonzero, the picture is scaled, preserving aspect ratio.

The offsets and sizes are given in PostScript units (big points).

Including headers from TEX

In order to get a particular graphic file to work, a certain font or header file might need to be run first. The dvips program provides support for this with the header \special. For instance, to cause procedures.ps be brought in, write: \special{header=procedures.ps} As another example, if you have some PostScript code that uses a PostScript font not built into your printer, you must download it to the printer. If the font isn't used elsewhere in the document, Dvips cannot know you've used it, so you must include it in the same way, as in: \special{header=putr.pfa} to include the font definition file for Adobe Utopia Roman. The header also special allows for specifying some additional code that should be inserted into the PostScript document before and after the file itself, as follows: \special{header={<filename>.ps} pre={<pre-code>} post={<post-code>}} This will insert pre-code just before <filename>.ps and post-code just after. It is required to use the (balanced) braces in all of the arguments, including the header, when using this extended syntax. This allows, for instance, dynamic headers, where some of the content depends on settings from the user in (La)TEX. Another application is the inclusion of graphics inside the PostScript header, so that they can be reused throughout the document, as with logs. That avoids including the same graphic several times.

Literal PostScript

For simple graphics, or just for experimentation, literal PostScript code can be included. Simply use a \special beginning with a double quote character '"'; there is no matching closing '"'.

Generally, Dvips encloses specials in a PostScript save/restore pair, guaranteeing that the special will have no effect on the rest of the document. The ps special, however, allows you to insert literal PostScript instructions without this protective shield; you should understand what you're doing (and you shouldn't change the PostScript graphics state unless you are willing to take the consequences). This command can take many forms because it has had a torturous history; any of the following will work:

\special{ps:<text>}
\special{ps::<text>}
\special{ps::[begin]<text>}
\special{ps::[end]<text>}
\special{ps::[nobreak]<text>}

You can download literal PostScript header code in your TEX document, for use with (for example) literal graphics code that you include later. The text of a \special beginning with an '!' is copied into the output file. A dictionary SDict will be current when this code is executed; Dvips arranges for SDict to be first on the dictionary stack when any PostScript graphic is included, whether literally (the '"' special) or through macros (e.g., epsf.tex). For example: \special{! /reset { 0 0 moveto} def}

\special{ps:
      [ /Rect [602 1083 1087 1320]
        /Border [0 0 2]
        /Color [1 0 0]
        /Dest link_child_page
        /Subtype /Link
        /ANN pdfmark
   } 

PostScript hooks

Besides including literal PostScript at a particular place in your document (as described in the previous section), you can also arrange to execute arbitrary PostScript code at particular times while the PostScript is printing. If any of the PostScript names bop-hook, eop-hook, start-hook, or end-hook are defined in userdict, they will be executed at the beginning of a page, end of a page, start of the document, and end of a document, respectively.

When these macros are executed, the default PostScript coordinate system and origin is in effect. Such macros can be defined in headers added by the -h option or the header= special, and might be useful for writing, for instance, DRAFT across the entire page, or, with the aid of a shell script, dating the document. These macros are executed outside of the save/restore context of the individual pages, so it is possible for them to accumulate information, but if a document must be divided into sections because of memory constraints, such added information will be lost across section breaks.

The single argument to bop-hook is the physical page number; the first page gets zero, the second one, etc. bop-hook must leave this number on the stack. None of the other hooks are passed arguments.

As an example of what can be done, the following special will write a light grey DRAFT across each page in the document:

\special{!userdict begin
  /bop-hook{
    gsave
      200 30 translate
      65 rotate
      /Times-Roman findfont 216 scalefont setfont
      0 0 moveto
      0.7 setgray (DRAFT) show
    grestore
  } def
end}

(Using bop-hook or eop-hook to preserve information across pages breaks compliance with the Adobe document structuring conventions, so if you use any such tricks, you may also want to use the -N option to turn off structured comments (such as %%Page). Otherwise, programs that read your file will assume its pages are independent.)

HyperTeXt

Dvips has support for producing hypertext PostScript documents. If you specify the -z option, the html: specials described below will be converted into pdfmark PostScript operators to specify links. Without -z, html: specials are ignored.

The resulting PostScript can then be processed by a distiller program to make a PDF file. (It can still be handled by ordinary PostScript interpreters as well.) Various versions of both PC and Unix distillers are supported; Ghostscript includes limited distiller support.

Arthur Smith (apsmith@aps.org), Tanmoy Bhattacharya, and Paul Ginsparg originally proposed and implemented the following specials:

html:<a href="xurl">
html:<a name="name">
html:</a>
html:<img src="xurl">
html:<base href="xurl">

href

Creates links in your TEX document. For example: \special{html:<a href="http://www.tug.org/">}\TeX\ Users Group\special{html:</a>}. The user will be able to click on the text TEX Users Group while running Xdvi and get to the TUG home page. (By the way, this is for illustration. In practice, you most probably want to use macros to insert the \special commands.)

name

Defines URL targets in your TEX documents, so links can be resolved. For example: \special{html:<a name="paradise">}Paradise\special{html:</a>} is exactly where you are right now.

This will resolve an href="#paradise". You'll also have to change the catcode of '#', etc. It's usually easiest to use existing macro packages which take care of all the details.

img

Links to an arbitrary external file. Interactively, a viewer is spawned to read the file according to the file extension and your mailcap file (see the Xdvi documentation).

base

Defines a base URL that is prepended to all the name targets. Typically unnecessary, as the name of the DVI file being read is used by default.

Color

Besides the source code support itself, there are additional TEX macro files: colordvi.tex and blackdvi.tex (and corresponding .sty versions for use with LaTeX).

All the color macro commands are defined in colordvi.tex (or colordvi.sty). To access these macros simply add to the top of your plain TEX file the command: \input colordvi.

These macros provide two basic kinds of color macros: ones for local color changes (a few words, a single symbol) and one for global color changes (the whole document). All the color names use a mixed case scheme to avoid conflicts with other macros. There are 68 predefined colors, with names taken primarily from the Crayola crayon box of 64 colors, and one pair of macros for the user to set his own color pattern. You can browse the file colordvi.tex for a list of the predefined colors. The comments in this file also show a rough correspondence between the crayon names and Pantones.

A local color command has the form \<ColorName>{<colored text>} where ColorName is the name of a predefined color, e.g., Blue. As shown, these macros take one argument, the text to print in the specified color.

The global color command has the form \textColorName. These macros take no arguments and changes the default color from that point on to ColorName.

The color commands will even work in math mode and across math mode boundaries. This means that if you have a color before going into math mode, the mathematics will be set in that color as well.

User-defined colors

There are two ways for the user to specify colors not already defined. For local changes, there is the command \Color which takes two arguments. The first argument is four numbers between zero and one and specifies the intensity of cyan, magenta, yellow and black (CMYK) in that order. The second argument is the text that should appear in the given color. For example, suppose you want the words this color is pretty to appear in a color which is 50% cyan, 85% magenta, 40% yellow and 20% black. You would use the command: \Color{.5 .85 .4 .2}{this color is pretty}. For global color changes, there is a command \textColor which takes one argument, the CMYK quadruple of relative color intensities. For example, if you want the default color to be as above, then the command \textColor{.5 .85 .4 .2} The text from now on will be this pretty color will do the trick.

\headline{\Black{My Header}}
\footline{\Black{\hss\tenrm\folio\hss}}

Color support details

To support color, Dvips recognizes a certain set of specials. These specials start with the keyword color or the keyword background, followed by a color specification.

What is a color specification? One of three things. First, it might be a PostScript procedure as defined in a PostScript file that sets the current color to some value. To set it to maroon, Maroon procedure is defined as 0 0.87 0.68 0.32 setcmykcolor.

The second possibility is the name of a color model (initially, one of rgb, hsb, cmyk, or gray) followed by the appropriate number of parameters. When Dvips encounters such a macro, it sends out the parameters first, followed by the string created by prefixing TeXcolor to the color model. Thus, the color specification rgb 0.3 0.4 0.5 would generate the PostScript code 0.3 0.4 0.5 TeXrgbcolor.

The third and final type of color specification is a double quote followed by any sequence of PostScript. The double quote is stripped from the output. For instance, the color specification "AggiePattern setpattern will set the color to the Aggie logo pattern (assuming such exists.)

I shall describe the background special first, since it is the simplest. The background keyword must be followed by a color specification. That color specification is used as a fill color for the background. The last background special on a page is the one that gets issued, and it gets issued at the very beginning of the page, before any text or specials are sent.

The color special itself has three forms. The first is just color followed by a color specification. In this case, the current global color is set to that color; the color stack must be empty when such a command is executed. The second form is color push followed by a color specification. This saves the current color on the color stack and sets the color to be that given by the color specification. This is the most common way to set a color. And the third is just color pop, with no color specification; this says to pop the color last pushed on the color stack from the color stack and set the current color to be that color.

Dvips correctly handles these color specials across pages, even when the pages are repeated or reversed.

Why not generate PDF from PS from DVI?

Because by the time TEX has shipped out a completed page of DVI, much potentially useful information has already been lost. Only by modifying TEX to output PDF directly, and by integrating the generation of PDF with TEX's "digestive tract", can such information be retained and captured within the PDF file. This allows, for example, an extremely simple and elegant implementation of hyperlinks, the beginning and end of which can span multiple lines or even pages. To accomplish this using DVI as an interlanguage requires heavy use of \specials and even then some functionality is lost unless TEX is modified. PDF also allows the re-use of (potentially large) data structures, a concept completely unknown within DVI.

Because the PDF which is generated by pdfTEX is usually more compact than that generated using DVI as an interlanguage, since only TEX has detailed knowledge of the data structures (boxes, etc.) of which the PDF is a representation.

(And finally, because only by integrating PDF generation within TEX itself can we gain access to the font-mutating possibilities which may in the future allow the implementation of dynamic font mutation for microjustification, etc.)

Basics

When PDF output is selected, TEX's \special command is ignored (that is, it does not contribute anything to the page(s) being shipped out, although its other, more subtle, effects still take place). A new primitive, \pdfliteral, allows raw PDF to be inserted into the PDF output stream at well-defined points.

pdfTEX allows the direct inclusion of bitmap graphics (as opposed to bitmap fonts). Graphics for inclusion must be expressed in PNG (Portable Network Graphics) format. Although facilities for the inclusion of EPS images are thought highly desirable by many, the overheads of PostScript interpretation make this an unreasonably demanding task. More likely is the development of a facility for the incorporation of (E)PDF images, but this is not currently implemented. Hans Hagen and Tanmoy Bhattacharya have developed a suite of macros which allow the inclusion of both METAPOST output and of a subset of PDF files (those that do not contain fonts, bitmaps and/or similar resources).

Hyperlinks

One of the most powerful features of the PDF format is the ability to establish both intra- and inter-document hyperlinks. This facility is accessible to pdfTEX users who have only to tag their documents to indicate the start, end and target of the link. All of the underlying housekeeping is performed by pdfTEX itself, including taking care of such difficulties as intervening line and/or page breaks. The only requirement is that the hyperlink shall start and end at the same level of box nesting. Any and all intervening boxes of the same depth are treated as a part of the hyperlink, but boxes nested to a greater depth are not.

Diacritics, escaped sequences, and special characters

Some languages are written or typed in a richer character set than ASCII. In Spanish, a vowel may bear an acute accent ('á' and so on), and there is also 'ñ' '¡', '¿' and 'ü'. Other languages have grave accents, or hat accents. So most non-ASCII characters can be produced by accenting an ASCII character.

Since XSLT does not perform character transactions, these might be effected by means of regular expressions applied either before or after creating your TeX file. Most text editors include a Replace feature but it would take too much time to transform your handful of non-ASCII characters whenever you want to test the end result to, say, proof it. Hence you had better write a script that performs the transformations with one key stroke. Also, you probably want the result stored in a differently-named file.

My tool of choice for this task is sed. Here is a handy script for Spanish to take your file from XML characters to TeX:

s/á/\\'a/g
s/é/\\'a/g
s/í/\\'\i{}/g
s/ó/\\'o/g
s/ú/\\'u/g
s/ü/\\"u/g
s/ñ/\\~n/g
s/Á/\\'A/g
s/É/\\'E/g
s/Í/\\'I/g
s/Ó/\\'O/g
s/Ú/\\'U/g
s/Ü/\\"U/g
s/Ñ/\\~N/g
s/¿/\\?`/g
s/¡/\\!`/g  

Another sed script for non-Spanish non-ASCII character transformations is:

s/ä/\\"a/g
s/æ/\\ae{}/g
s/è/\\`e/g
s/ë/\\"e /g
s/ï/\\"\\i{}/g
s/ö/\\"o/g
s/ø/\\o{}/g
s/Ø/\\O{}/g
s/Æ/\\AE{}/g
s/È/\\`E/g
s/Ö/\\"O/g
s/ß/\\ss{}/g
s/ç/\\c c/g
s/Ç/\\c C/g 

Mathematical formulas

DocBook, which is just an XML vocabulary, includes tags equation, informalequation, and inlineequation, as well as mathphrase for simple mathematics equations that do not require extensive markup. Whatever the differences and nuances of usage, you may implement a scheme for typing TeX mathematical code in your XML. I suggest that you use a format attribute in your mathematical tags to cause the XSLT processor to include or exclude mathematical elements selectively. For example:

<equation format='non-tex'><varname>x</varname><superscript>2</superscript> = -1</equation>
<equation format='tex'>$$x^2 = -1$$</equation>

...

Providing a Bounding Box

If you want to provide your own bounding box (figure size), use a call something like this:

\epsfbox[10 30 150 80]{whatever.eps}

The four numbers in square brackets tell TeX to use only part of the size of the graphic. In this example, TeX would pretend that only the rectangle from (10,30) to (150,80) is actually used. The dimensions are points, so the graphic would have an effective size (for TeX' purposes) of (150-10) or 140 points wide by (80-30) or 50 points tall.

The graphic is not actually cropped to the given size, it is only shifted on the page so that the lower left corner of the bounding box coincides with the lower left corner of the area TeX reserves for it. In the example above, location (10,30) in the figure would be located at the lower left corner of the box in which TeX places the figure, but any part of the image outside the rectangle from (10,30) to (150,80) would still appear on the page.

%%BoundingBox: 0 0 360 72

Scaling the Included EPS File

To scale a figure, use put the line:

\epsfxsize=<dimen>

before the \epsffile{} or \epsfbox{} command. You may use any standard TeX dimension units, though the system may default to points (pt). This command specifies the horizontal dimension, and the vertical dimension scales proportionally.

A Simple Structured-Text Example

Now, let's try something more complicated:

\mainlanguage[fi]
\starttext
  \completecontent

  \part{Something}
    Lorem ipsum
    \chapter{Something else}
      Dolor sit amet

\stoptext

Now we've set to Finnish both the hyphenation and the auto generated element names (such as Table of Contents). We've also defined a part and a chapter, and generated a ToC with the \completecontent command.

A More Advanced Structured-Text Example

Here we will additionally be using the macros \startsection[title={name}] and \stopsection to mark the title and the content of a section. So

\starttext
  \startsection[title={Testing ConTeXt}]
    This is my {\em first} ConTeXt document.
  \stopsection
\stoptext

A Still Richer Example

Here is another example from the wikipedia page:

% This line is a comment because % precedes it.
% It specifies the format of head named 'title'
% Specifically the style of the font: sans serif
% + bold + big font.

\setuphead[title][style={\ss\bfd},
    before={\begingroup},
    after={John Doe, the author\smallskip%
           \currentdate\bigskip\endgroup}]

\starttext

\title{\CONTEXT}

\section{Text}
\CONTEXT\ is a document preparation system for the
\TEX\ typesetting program. It offers programmable
desktop publishing features and extensive
facilities for automating most aspects of
typesetting and desktop publishing, including
numbering and cross-referencing (for example to
equation \in[eqn:famous-emc]), tables and figures,
page layout, bibliographies, and much more.

It was originally written around 1990 by Hans
Hagen. It could be an alternative or complement
to \LATEX.

\section{Maths}
With \CONTEXT\ we could write maths. Equations
can be automatically numbered.

\placeformula[eqn:famous-emc]
\startformula
    E = mc^2
\stopformula
with
\placeformula[eqn:def-m]
\startformula
    m = \frac{m_0}{\sqrt{1-\frac{v^2}{c^2}}}
\stopformula

\stoptext

ConTeXt Top Ten Commands

A novice user might be put off by the number of ConTeXt commands. Satisfying results can be obtained by only using the next ten groups of commands:

\starttext, \stoptext
\chapter, \section, \title, \subject, \setuphead, \completecontent
\em, \bf, \cap
\startitemize, \stopitemize, \item, \head
\abbreviation, \infull, \completelistofabbreviations
\placefigure, \externalfigure, \useexternalfigures
\placetable, \starttable, \stoptable
\definedescription, \defineenumeration
\index, \completeindex
\setuplayout, \setupfootertexts, \setupheadertexts

Before you start...

Placing a font switch at the begin of a paragraph can sometimes generate unexpected side-effects. This can be avoided by forcing horizontal mode before any font change:

\dontleavehmode{\bf Warning!} Care must be taken when a font switch is used at the beginning of a paragraph.\par

It is usually a bad style to use explicit font switches in the text. It is better to define a semantic command that takes care of the font switching. For example, instead of using {\bf\red important text}

\definehighlight[important][style=bold, color=red]

and then use \important{important text} in the text.

Font styles and alternatives

There are three main types of font styles: serif, sans serif, and teletype. To switch between these styles, use \rm for serif, \ss for sans serif, and \tt for teletype.

Each of these styles comes in different alternatives: normal, bold, italic, slanted, bold-italic, bold-slanted, and small-capped. To switch to a different alternative, use \tf (typeface) for normal, \bf for bold, \it for italic, \sl for slanted, \bi for bold-italic, \bs for bold-slanted, and \sc for small-capped.

You can generally combine font styles with alternatives, so if you want to switch to bold sans serif, you can use either \bf\ss or \ss\bf.

A font switch remains valid for the rest of the group. So, if you want to temporarily switch to a different font, use the font style command inside a group. The easiest way to start a group is to enclose the text within braces (also called curly brackets), for example

This is serif text
{\ss This is sans serif}
This is serif again
{\tt and this is typewriter}
And serif again

Emphasizing text

There is a font switch \em to emphasize text. This is somewhat special: it does automatic italic correction and changes the alternative depending on the current alternative. For example, if the current font alternative is normal (i.e. upright), \em switches to slanted; and if the current font alternative is slanted, \em switches to normal.

ConTeXt uses the Latin Modern fonts by default; these fonts look similar to the original Computer Modern fonts, but have a much larger character repertoire. As it happens, in the Latin Modern (and Computer Modern) fonts, the slanted font does not stand out from the upright font enough for some tastes; so, many people prefer to use the italic font for emphasis. To do that use

\definebodyfontenvironment[default][em=italic]

\definefontfeature[default][default][itlc=yes]

ConTeXt Font Sizes

Occasionally one needs to use a font size different from the bodyfont. ConTeXt provides two series of commands for that. For a larger font size, you can use \tfa to scale the font size by a factor of 1.2, \tfb to scale by a factor of (1.2)^2 = 1.44, \tfc to scale by (1.2)^3 = 1.728 and \tfd to scale by (1.2)^4 = 2.074. The scale is relative to the current bodyfont size.

To decrease the font size, you can use \tfx to scale the font by a factor of 0.8 and \tfxx to scale by a factor of 0.6.

The mapping of particular command suffixes (a, x, etc.) and current bodyfont size to effective font size can be changed by \definebodyfontenvironment. The default values defined in font-ini are:

\definebodyfontenvironment
  [\s!default]
  [        \s!text=1.0,
         \s!script=0.7,
   \s!scriptscript=0.5,
              \c!a=1.200,
              \c!b=1.440,
              \c!c=1.728,
              \c!d=2.074,
                 *=\currentfontscale, % wildcard
              \c!x=0.8,
             \c!xx=0.6,
            \c!big=1.2,
          \c!small=0.8,
 \c!interlinespace=,
             \c!em=\v!slanted]

It is also possible to set the scaling factors for specific font sizes. For example, if you want \tfa to set the effective font size to 12pt when the bodyfont size is 10pt, and to set the effective font size to 14pt when the bodyfont size is 11pt, then add

\definebodyfontenvironment [10pt] [a=12pt]
\definebodyfontenvironment [11pt] [a=14pt]

\definebodyfontenvironment is described in detail in the ConTeXt manual and the font-ini source file.

Font size can be combined with font styles. As a shortcut, you can use \bfa to get bold font scaled by 1.2, \bfx to get a bold font scaled by 0.8 and similar commands for other font styles.

These quick font switches are meant for changing the font style, alternative, or size of a few words: they do not change the bodyfont, so they don't affect interline spacing or math font sizes. So, if you want to change the font size of an entire paragraph, use \switchtobodyfont described below in Complete Font Change. However, it is fine to use them as style directives in setup commands, that is, using them as an option for style=... in any setup command that accepts style option.

Mnemonic font switches

While learning a document markup language like ConTeXt, it can be hard to remember all the commands. ConTeXt provides other, easy-to-remember font switches. So for bold you can use \bold, for italic you can use \italic, for slanted you can use \slanted, and so on. You can probably guess what the following do:

\normal
\slanted
\boldslanted
\slantedbold
\bolditalic
\italicbold
\small
\smallnormal
\smallbold
\smallslanted
\smallboldslanted
\smallslantedbold
\smallbolditalic
\smallitalicbold
\sans
\sansserif
\sansbold
\smallcaps

In addition, the commands \smallbodyfont and \bigbodyfont can be used to change the font size. The relative size depends on the value of big and small in \definebodyfontenvironment.

These mnemonic font switches are pretty smart. You can either use them as font style switches inside a { group }, or as a font changing command that takes an argument. For example,

This is {\bold bold} and so is \bold{this}. But this is not.

These mnemonic font switches can also be used for all style=... options, and while using them as style options, you can just give the command name without the backslash. For example:

\setuphead[section][style=bold]

Complete Font (BodyFont) Change

If you need to change to a different font size and take care of interline spacing, you can change the bodyfont by using \switchtobodyfont. For example, to switch to 12pt you can use \switchtobodyfont[12pt].

ConTeXt provides two relative sizes, called big and small. So, to increase the bodyfont size, use \switchtobodyfont[big] (or \setbigbodyfont), and to decrease the bodyfont size, use \switchtobodyfont[small] (or \setsmallbodyfont). The exact size used for big and small can be set using \definebodyfontenvironment.

The \setupbodyfont command accepts all the same arguments as \switchtobodyfont. The difference between the two is that \setupbodyfont also changes the font for headers, footers and other page markings, while \switchtobodyfont does not. So you should use \setupbodyfont for global font definitions to apply to the whole document, and \switchtobodyfont for local font changes (i.e. changes to the running text only). The effect of \switchtobodyfont can be localized within a group as usual.

Simple Typescript Example

This section describes how to map a Sans Serif font to the \ss command and a Serif font to the \rm command. This section also describes how typefaces differ from typescripts.

mtxrun --script fonts --list --all --pattern=nimbus*

% Enable Unicode fonts
\enableregime[utf]

% Enable Capital Letter use
\setupcapitals[sc=yes]

% Define a script named [serif][nimbus]
\starttypescript [serif] [nimbus]
  \definefontsynonym [Serif]             [name:nimbusromno9lregu]
  \definefontsynonym [SerifBold]         [name:nimbusromno9lbold]
  \definefontsynonym [SerifItalic]       [name:nimbusromno9lreguital]
  \definefontsynonym [SerifSlanted]      [name:nimbusromno9lreguital]
  \definefontsynonym [SerifBoldItalic]   [name:nimbusromno9lboldital]
  \definefontsynonym [SerifBoldSlanted]  [name:nimbusromno9lboldital]
  \definefontsynonym [SerifCaps]         [name:nimbusromno9lregu]
\stoptypescript

% Define a second script named [sans][nimbus]
\starttypescript [sans] [nimbus]
  \definefontsynonym [Sans]             [name:nimbussanlregu]
  \definefontsynonym [SansBold]         [name:nimbussanlbold]
  \definefontsynonym [SansItalic]       [name:nimbussanlreguital]
  \definefontsynonym [SansSlanted]      [name:nimbussanlreguital]
  \definefontsynonym [SansBoldItalic]   [name:nimbussanlboldital]
  \definefontsynonym [SansBoldSlanted]  [name:nimbussanlboldital]
  \definefontsynonym [SansCaps]         [name:nimbussanlregu]
\stoptypescript

% Define the typeface nimbus; use serif for rm-fonts, sans serif for ss-fonts.
\definetypeface [nimbus]  [rm]  [serif] [nimbus]
\definetypeface [nimbus]  [ss]  [sans]  [nimbus]

% Indicate the typeface to use.
\usetypescript[nimbus][uc]
\setupbodyfont[nimbus,rm,10pt]

\starttext

Regular, {\it Italic}, {\bf Bold}, {\bi Bold-Italic}, {\sc KaPiTaLe}

\showbodyfont

\stoptext

...
\definefontsynonym [SansCaps]           [name:nimbusromno9lregu]
\stoptypescript

% Define a typescript named nimbus.
\starttypescript [nimbus]
  \definetypeface [nimbus]	[rm]	[serif]	[nimbus]
  \definetypeface [nimbus]	[ss]	[sans]	[nimbus]
\stoptypescript

% Use the nimbus typescript, which defines the nimbus typeface.
\usetypescript[nimbus]
\setupbodyfont[nimbus,rm,10pt]

\starttext
...

\definetypeface [nimbus]  [rm]  [serif]  [nimbus]
 \definetypeface [nimbus]  [ss]  [sans]   [nimbus]

Linux Libertine on MKIV

Starting from Context 2010.05.21 there is the libertine typescript already defined. It points to the fonts shipped with TeXlive2010 (they have a different name than the upstream). You have to define script=latn if you want the ligatures in the Bold Italic font (until the upstream doesn't set a default script). See http://archive.contextgarden.net/thread/20101108.150757.a6a9040d.en.html

% use microtypography
\definefontfeature[default][default][protrusion=quality,expansion=quality,script=latn]
\usetypescript[libertine]
\setupalign[hz,hanging]

\setupbodyfont[libertine,10pt]

\starttext
  \input tufte
\stoptext

The complete code, which should work for ConTeXt shipped with TeXlive 2010 is:

\definefontfeature[default][default]
                  [protrusion=quality,
                    expansion=quality,
                    script=latn]

\starttypescriptcollection[linuxlibertine]

    \starttypescript [serif] [linuxlibertine]
        \definefontsynonym [Libertine-Regular]    [file:fxlr.otf]
        \definefontsynonym [Libertine-Italic]     [file:fxlri.otf]
        \definefontsynonym [Libertine-Bold]       [file:fxlb.otf]
        \definefontsynonym [Libertine-BoldItalic] [file:fxlbi.otf]
    \stoptypescript

    \starttypescript [serif] [linuxlibertine] [name]
        \setups[font:fallback:serif]
        \definefontsynonym [Serif]           [Libertine-Regular]    [features=default]
        \definefontsynonym [SerifItalic]     [Libertine-Italic]     [features=default]
        \definefontsynonym [SerifBold]       [Libertine-Bold]       [features=default]
        \definefontsynonym [SerifBoldItalic] [Libertine-BoldItalic] [features=default]
        \definefontsynonym [SerifCaps]       [Libertine-Regular]    [features=smallcaps]
    \stoptypescript

    \starttypescript [sans] [biolinum]
        \setups[font:fallback:sans]
        \definefontsynonym [Biolinum-Regular]    [file:fxbr.otf]
        \definefontsynonym [Biolinum-Bold]       [file:fxbb.otf]
        \definefontsynonym [Biolinum-Italic]     [file:fxbri.otf]
        \definefontsynonym [Biolinum-Slanted]    [file:fxbro.otf]
        \definefontsynonym [Biolinum-BoldItalic] [file:fxbbo.otf]
    \stoptypescript

    \starttypescript [sans] [biolinum] [name]
        \setups[font:fallback:sans]
        \definefontsynonym [Sans]           [Biolinum-Regular]    [features=default]
        \definefontsynonym [SansBold]       [Biolinum-Bold]       [features=default]
        \definefontsynonym [SansItalic]     [Biolinum-Italic]     [features=default]
        \definefontsynonym [SansSlanted]    [Biolinum-Slanted]    [features=default]
        \definefontsynonym [SansBoldItalic] [Biolinum-BoldItalic] [features=default]
        \definefontsynonym [SansCaps]       [Biolinum-Regular]    [features=smallcaps]
    \stoptypescript

    \starttypescript [linuxlibertine]
        \definetypeface [linuxlibertine] [rm] [serif] [linuxlibertine] [default]
        \definetypeface [linuxlibertine] [ss] [sans]  [biolinum]  [default]
        \definetypeface [linuxlibertine] [tt] [mono]  [default]   [default]
        %definetypeface [libertine] [mm] [math]  [times]     [default]
        \quittypescriptscanning
    \stoptypescript

\stoptypescriptcollection

\usetypescript[linuxlibertine]
\setupbodyfont[linuxlibertine,10pt]
% use the microtype
\setupalign[hz,hanging]

\starttext
  \input tufte
\stoptext

Long quotations and Extracts*

Nested Quotations*

(For alternate nesting of double and single quotes.)