On Sat, 25 Jun 2016, Wolfgang Schuster wrote:
Aditya Mahajan <mailto:adit...@umich.edu>
25. Juni 2016 um 18:37
On Sat, 25 Jun 2016, Hans Hagen wrote:
So, to a newcomer, one can suggest to simply use components and
environments. What is the advatange of the extra structure provided by
product/project?
A product is the book itself while components are only chapters, sections
etc. (components can be nested).
Does that mean products cannot be nested?
Even if a component is part of a product, the component must explicitly
include all the environments needed for compilation (rather than simply
refering to a product, as in the original question). So, I don't
structurally see an advantage of the product-component distinction.
Since this is an old mechanism and widely used (though I have never used
it), I am missing something. The wiki page is woefully out of date with
the current behavior.
Aditya
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
