From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: Re[2]: Environments, Projects, Products, Components
Date: Thu, 31 May 2001 10:11:24 +0200 [thread overview]
Message-ID: <3.0.6.32.20010531101124.01a48500@server-1> (raw)
In-Reply-To: <25874768.20010530200158@bigfoot.com>
At 08:01 PM 5/30/01 +0200, Giuseppe Bilotta wrote:
>I see. Hadn't thought of that ... which do you think is the better
>idea? taking \product off is space-saving (only one file per
>chapter, instead of two wrappers plus the file), but somehow seems
>less structuring ... maybe I'd better keep \product in until I
>need to use the same file somewhere else ...
>
>What happens if product booka meets a component that says \product
>bookb?
there are also locale env's that can be loaded per product so in that case
you may waqnt the directive so that context can backtract the doc tree.
some day this will be more extensive [split doc processing and auto cross
doc/toc refs and so]
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
next prev parent reply other threads:[~2001-05-31 8:11 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-30 11:40 Giuseppe Bilotta
2001-05-30 15:14 ` Taco Hoekwater
2001-05-30 18:01 ` Re[2]: " Giuseppe Bilotta
2001-05-31 7:51 ` Taco Hoekwater
2001-05-31 9:34 ` Hans Hagen
2001-08-30 17:54 ` Steve Lumos
2001-08-31 7:19 ` Hans Hagen
2001-05-31 8:11 ` Hans Hagen [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-25 18:14 Broken catcodes Giuseppe Bilotta
2002-05-25 20:17 ` Hans Hagen
2002-05-25 21:46 ` Re[2]: " Giuseppe Bilotta
2002-05-26 17:39 ` Hans Hagen
2002-05-26 20:38 ` Re[3]: " Giuseppe Bilotta
[not found] ` <pragma@wxs.nl>
2001-03-12 16:50 ` fonts fonts and fonts Hans Hagen
2001-03-12 17:07 ` Frans Goddijn
2001-03-12 23:11 ` Christoph Dreyer
2001-03-13 9:33 ` S2P development
2001-03-13 10:12 ` Han The Thanh
2001-03-13 10:35 ` Hans Hagen
2001-03-14 21:32 ` H. Ramm
2001-03-13 7:12 ` Steve Lumos
2001-03-13 9:13 ` Hans Hagen
2001-03-14 0:29 ` Uwe Koloska
2001-03-13 14:35 ` Ed L Cashin
2001-03-14 0:18 ` Uwe Koloska
2001-03-15 21:55 ` H. Ramm
2002-05-27 15:27 ` Re[2]: Broken catcodes Daniel Flipo
2002-05-27 15:32 ` Hans Hagen
2001-02-22 7:24 Horizontal centering \startlines...\stoplines Steve Lumos
2001-02-22 8:47 ` Horizontal centering \startlines...\stoplines / poems Hans Hagen
2001-03-03 9:22 ` Steve Lumos
2001-03-04 21:09 ` Hans Hagen
2001-03-07 4:08 ` Steve Lumos
2001-03-07 8:14 ` Hans Hagen
2000-08-19 12:21 Setting up footnotes Joop Susan
2000-08-21 11:00 ` Hans Hagen
2000-08-21 18:19 ` Joop Susan
2000-08-22 6:59 ` 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=3.0.6.32.20010531101124.01a48500@server-1 \
--to=pragma@wxs.nl \
--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).