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 -------------------------------------------------------------------------