29.05.2014 Views

ConTEXt the manual Hans Hagen - Pragma ADE

ConTEXt the manual Hans Hagen - Pragma ADE

ConTEXt the manual Hans Hagen - Pragma ADE

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Documents 17<br />

content<br />

index<br />

commands<br />

macros<br />

Documents<br />

2.1 Introduction<br />

Why should one use T E X in <strong>the</strong> first place? Many people start using T E X because <strong>the</strong>y want to<br />

typeset math. O<strong>the</strong>rs are charmed by <strong>the</strong> possibility of separating content and make--up. Yet<br />

ano<strong>the</strong>r kind of user longs for a programmable system. And let us not forget those users that<br />

go for quality.<br />

When using T E X one does not easily run into capacity problems. Typesetting large documents<br />

with hundreds of pages is typically a job for T E X. If possible, when coding a document one<br />

should look beyond <strong>the</strong> current document. These days we see documents that were originally<br />

typeset for paper being published in electronic format. And how about making a stripped<br />

version of a 700 page document? A strict separation between content and layout (make--up)<br />

on <strong>the</strong> one hand and an acceptable redundancy in structure on <strong>the</strong> o<strong>the</strong>r is often enough to<br />

guarantee multiple use of one document source.<br />

A system like ConT E Xt is meant to make life easier. When coding a document <strong>the</strong> feeling<br />

can surface that “this or that should be easier”. This feeling often reflects <strong>the</strong> truth and <strong>the</strong><br />

answer to <strong>the</strong> question can often be found in this <strong>manual</strong>, although sometimes obscured. It<br />

takes some time to learn to think in structure and content, certainly when one is accustomed<br />

to mouse driven word processors. In this chapter we focus on <strong>the</strong> structure of collections of<br />

documents.<br />

2<br />

2.1 Introduction 17<br />

2.2 Start and stop 17<br />

2.3 Structure 18<br />

2.4 Directories 23<br />

2.5 Versions 23<br />

2.6 Modes 24<br />

2.2 Start and stop<br />

In a self contained text we use <strong>the</strong> following commands to mark <strong>the</strong> begin and end of a text:<br />

\starttext<br />

\stoptext<br />

The first command takes care of a number of initializations and <strong>the</strong> last command tells T E X<br />

that processing can stop. When this command is left out T E X will display a * (a star) on <strong>the</strong><br />

command line at <strong>the</strong> end of <strong>the</strong> job. T E X will expect a command, for example \end.<br />

It is advisable to type <strong>the</strong> document setups before <strong>the</strong> \start--command, <strong>the</strong> so called setup<br />

area of <strong>the</strong> document. In this way a clever word--processor can identify where <strong>the</strong> text starts,<br />

and <strong>the</strong>refore can include those setups when it partially processes <strong>the</strong> document, given of<br />

course that it supports partial processing of files.<br />

search go back exit<br />

Introduction — Start and stop 2

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!