From: Hans Hagen <pragma@wxs.nl>
Subject: Re: naming relative paths within a project
Date: Wed, 12 Mar 2003 00:31:15 +0100 [thread overview]
Message-ID: <5.1.0.14.1.20030312002655.03320008@server-1> (raw)
In-Reply-To: <u4r6t6fz0.fsf@multiline.com.au>
Hi,
Indeed you need to add the (relative) path, simply because tex cannot ask
for a directory (well, now i think of it, it can by using a sys call;
actually i do have a script that generates an xml path structure, so maybe
i can add that as feature some day)
if your filenames are unique, you can omit the paths and say:
\usepath[BodyMatter]
\usepath[FrontMatter]
context does look for files at . and .. and ../.. and ../../..
(configurable depth)
Hans
At 08:05 PM 2/24/2003 +0800, you (Guy) wrote:
>I've got a very short question, but coupled to a very long
>explanation, my question is: when referencing a component file from
>within a product file (and given that the component file is stored in
>the same directory as the product file, which is in a sub-directory
>below my project file) must I include the relative path of the component
>file from my project directory, through my sub-directories to my
>component file, or can I just refer to the component's filename.
>
>Now here is the actual example. I've done a little bit of ASCII
>artwork below showing the directory structure that I'm following. My
>artwork isn't the best, so I've also include some explanation.
>
>Project
> |
> ---- EnviromentPageLayout.tex (global environment file)
> |
> ---- Project.tex (project file)
> |
> |----|
> | FrontMatter (directory)
> | |
> | ---- EnvironmentFrontMatter.tex (local environment file)
> | |
> | ---- ProductFrontMatter.tex (product file)
> | |
> | ---- TitlePage.tex (component file)
> | |
> | ---- Contents.tex (component file)
> | |
> | ---- Preface (component file)
> |
> |----|
> | BodyMatter (directory)
> | |
> | ---- EnvironmentBodyMatter.tex (local environment file)
> | |
> | ---- ProductBodyMatter.tex (product file)
> | |
> | ---- Chapter01.tex (component file)
> | |
> | ---- Chapter02.tex (component file)
> | |
> |----|
> BackMatter (directory)
> |
> ---- EnvironmentBackMatter.tex (local environment file)
> |
> ---- ProductBackMatter.tex (product file)
> |
> ---- Appendix01.tex (component file)
> |
> ---- Index.tex (component file)
>
>
>In my Project directory I have two files:
>
> 1) EnvironmentPageLayout.tex
>
> If you are interested in an environment, the one I've based mine
> on is the one posted by David Arnold
>
> http://ml-archives.mini.pw.edu.pl/ntg-context/msg02853.html
>
> 2) Project.tex
>
> ----
>
> %project file
>
> \startproject Project
>
> \environment EnvironmentPageLayout
>
> \product FrontMatter/ProductFrontMatter
>
> \product BodyMatter/ProductBodyMatter
>
> \product BackMatter/ProductBackMatter
>
> \stopproject
>
> ---
>
> >From the project directory, I've created 3 sub-directories,
>FrontMatter, BodyMatter, and BackMatter and each of these
>sub-directories contains:
>
> 1) an Environment file
>
> 2) a Product file, for example, in the BodyMatter directory, I have
>
> -----
>
> % product file
>
> \startproduct ProductBodyMatter
>
> \project Project
>
> \environment BodyMatter/EnvironmentBodyMatter
>
> \startbodymatter
>
> \component BodyMatter/Chapter01
>
> \stopbodymatter
>
> \stopproduct
>
> -----
>
> 3) many Component files, for example, Chapter01.tex, in the BodyMatter
> directory, looks like:
>
> -----
>
> % component Chapter01
>
> \startcomponent Chapter01
>
> \project ProjectJavaXMLManuscript
>
> \product BodyMatter/ProductBodyMatter
>
> \chapter[introduction]{Introduction}
>
> \stopcomponent
>
> -----
>
>
>So my question in terms of the above structure, is: must I refer to
>each component in the product file by its full path name
>
> \component BodyMatter/Chapter01
>
>or can I refer to it, by just its file name
>
> \component Chapter01
>
>where Chapter01.tex is a file contained in a subdirectory of the
>project file.
>
>_______________________________________________
>ntg-context mailing list
>ntg-context@ntg.nl
>http://www.ntg.nl/mailman/listinfo/ntg-context
>
>================================================================
>Deze e-mail is door E-mail VirusScanner van Planet Internet gecontroleerd
>op virussen.
>Op http://www.planet.nl/evs staat een verwijzing naar de actuele lijst
>waar op wordt gecontroleerd.
-------------------------------------------------------------------------
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
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
prev parent reply other threads:[~2003-03-11 23:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 12:05 Guy Worthington
2003-03-11 23:31 ` Hans Hagen [this message]
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=5.1.0.14.1.20030312002655.03320008@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).