diff options
author | Taco Hoekwater <taco@elvenkind.com> | 2011-06-09 05:30:47 +0000 |
---|---|---|
committer | Taco Hoekwater <taco@elvenkind.com> | 2011-06-09 05:30:47 +0000 |
commit | 49a20b492a930e952807b9e61f50c3fd2b23355f (patch) | |
tree | fdd7baf8b81369b404d11a6b61313ef1bb3f6974 /Master/texmf-dist/doc/context/manuals/reference/en/co-documents.tex | |
parent | ad6b85844153367edc38e9f8725c50d765e41a1a (diff) |
new context reference manual
git-svn-id: svn://tug.org/texlive/trunk@22880 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf-dist/doc/context/manuals/reference/en/co-documents.tex')
-rw-r--r-- | Master/texmf-dist/doc/context/manuals/reference/en/co-documents.tex | 30 |
1 files changed, 18 insertions, 12 deletions
diff --git a/Master/texmf-dist/doc/context/manuals/reference/en/co-documents.tex b/Master/texmf-dist/doc/context/manuals/reference/en/co-documents.tex index cd9661c1c7a..8ffbce1e19c 100644 --- a/Master/texmf-dist/doc/context/manuals/reference/en/co-documents.tex +++ b/Master/texmf-dist/doc/context/manuals/reference/en/co-documents.tex @@ -237,15 +237,15 @@ documents that are placed on several subdirectories. \bf project \VL
\bf environment \VL
\bf product \VL
- \bf componnent \VL\SR
+ \bf component \VL\SR
\HL
\VL \type{\project <<name>>}
- \VL \VL \VL \yes \VL \yes \VL\FR
+ \VL \VL \VL (\yes) \VL (\yes) \VL\FR
\VL \type{\environment <<name>>}
\VL (\yes) \VL (\yes) \VL (\yes) \VL (\yes) \VL\MR
\VL \type{\product <<name>>}
\VL \yes \VL \VL \VL (\yes) \VL\MR
-\VL \type{\componentonderdeel <<name>>}
+\VL \type{\component <<name>>}
\VL \VL \VL (\yes) \VL (\yes) \VL\LR
\HL
\stoptable
@@ -323,10 +323,12 @@ independently, given that the stucture is defined properly. In principal a project file contains only a list of products
and environments. If you would process the project file all
products will be placed in one document. This is seldom
-wanted. This manual for example has a project structure.
-Every part is a product and every chapter is a component.
-There are several environments that are loaded in the main
-project file.
+wanted.
+
+If you have only one product, you don't really need a project file.
+This manual for example has a product/component structure without a project
+file. Every chapter is a component and the product file loads some
+environments.
Schematically the coherence between files could be
displayed as illustrated in \in {figures} [fig:structure
@@ -445,6 +447,9 @@ Below you will find an example of a project structure. \startbuffer
\startcomponent first
+\environment environ
+\product example
+
\part{One}
\completecontent
@@ -476,6 +481,9 @@ Below you will find an example of a project structure. \startbuffer
\startcomponent second
+\environment environ
+\product example
+
\part{Two}
\completecontent
@@ -505,10 +513,8 @@ Below you will find an example of a project structure. \stopfiguretext
The files \type{first.tex}, \type{second.tex} and
-\type{example.tex} can be processed separately. As long as
-there is one product in this project you can also process
-\type{project.tex}. If you process an environment there will
-be no pages of output.
+\type{example.tex} can be processed separately. If you process an environment
+there will be no pages of output.
\section[directories]{Directories}
\index{files+directories}
@@ -669,7 +675,7 @@ we spoil the document source with output and mode settings, the more flexible we are.
To enable users to develop a style that adapts itself to
-certain circumstances, \CONTEXT\ provide system modes. For
+certain circumstances, \CONTEXT\ provides system modes. For
the moment there are:
\starttabulate[|lT|p|]
|