From: "Procházka Lukáš Ing." <LPr@pontex.cz>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Product-component structure
Date: Mon, 11 Jul 2016 13:01:58 +0200 [thread overview]
Message-ID: <op.ykfnlkg53h68c7@lpr> (raw)
In-Reply-To: <alpine.OSX.2.02.1606251324370.87371@nqv-znpobbx>
Hello,
my "how-I-do-it" used for typesetting a large book was:
---- styles.sty
% Styles, settings etc.; never compiled individually, thus ".sty"; the file also doesn't use '\startenvironment' ... '\stopenvironment' commands (I even don't know whether such commands exist; anyway, I didn't need them)
\mainlanguage[cz]
...
----
---- book.tex
% Main file to build the whole book
\environment styles.sty
\startproduct *
\startfrontmatter
...
\stopfrontmatter
\startbodymatter
\component comp01
...
\stopbodymatter
\stopproduct
---- comp01.tex
% One of components; can be compiled individually, but sections are not numbered from the point of view of the final document (= book.tex) ("globally") but "locally" from the point of view of just comp01.tex
\environment styles.sty
\startcomponent *
...
\stopcomponent
Resume:
- Environment file 'styles.sty' is included in the product file and ALSO in all component files.
- Environment file is included AHEAD OF any \start{product|component}.
- Product file can be successfully compiled.
- Single components can be compiled successfully, too; sections here are NOT NUMBERED as in the final document.
- There no need to use "project" ability.
That's how I used and I understood component/product/project/environment structure in my project (book).
But a better way may exist (or might be intended).
Best regards,
Lukas
On Sat, 25 Jun 2016 19:25:32 +0200, Aditya Mahajan <adityam@umich.edu> wrote:
> On Sat, 25 Jun 2016, Wolfgang Schuster wrote:
>
>>> Hans Hagen <mailto:pragma@wxs.nl>
>>> 25. Juni 2016 um 11:56
>>>
>>>
>>> i always use one main environment (that can include others) and putting
>>> an \environment on top of a component is then not much overhead (compared
>>> to getting the content done)
>> The problem with puttins \environment before \startcomponents is
>> that you can’t check for the *component mode which is enabled
>> after the environment was loaded.
>
> So, one should use:
>
> \startcomponent *
> \environment env
> ...
> \stopcomponent
>
> for both components and products?
>
> Aditya
--
Ing. Lukáš Procházka | mailto:LPr@pontex.cz
Pontex s. r. o. | mailto:pontex@pontex.cz | http://www.pontex.cz
Bezová 1658
147 14 Praha 4
Tel: +420 241 096 751
Fax: +420 244 461 038
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2016-07-11 11:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 19:19 Aditya Mahajan
2016-06-24 22:20 ` Hans Hagen
2016-06-25 6:25 ` Wolfgang Schuster
2016-06-25 8:42 ` Aditya Mahajan
2016-06-25 9:56 ` Hans Hagen
2016-06-25 16:37 ` Aditya Mahajan
2016-06-25 17:10 ` Wolfgang Schuster
2016-06-25 17:24 ` Aditya Mahajan
2016-06-25 17:13 ` Wolfgang Schuster
2016-06-25 17:25 ` Aditya Mahajan
2016-07-11 11:01 ` Procházka Lukáš Ing. [this message]
2016-07-11 14:42 ` Alan BRASLAU
2016-06-26 9:34 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=op.ykfnlkg53h68c7@lpr \
--to=lpr@pontex.cz \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).