18
edits
Changes
Jump to navigation
Jump to search
Added some detailed information on compiling components and product files; Fixed the example
If you tex (compile) one single component (e.g. a chapter of a book) or product (e.g. one volume of a magazine), the environment file of the project is used.
In addition, you have to keep in mind that when compiling a product or component file, ConTeXt goes "up" to the project file and compiles everything it finds in there that is not a <cmd>product</cmd> (e.g. table of content, sectioning commands, text, <cmd>component</cmd> etc.). So all the things on project level have to be put inside a <cmd>product</cmd>, otherwise they will show up in the individual components (or products), too. That also makes it problematic to use <cmd>component</cmd> directly inside a project file, i.e. you have to use <cmd>product</cmd>, you can't skip it.
[[User:Hraban|Hraban]] uses and suggests the following naming conventions
\product prd_year2004-04
\completetableofcontentsproduct tableofcontent
\stopproject
