Hello! In some special cases I need to set paths for input files directly from ConTeXt code not from config file. In manuals \setupexternalfigures is described. Is there any similar command for files that are inputed directly by \input, \typefile \processXMLfile (the last is the most interesting for me) and similar commands? If there isn't any special command for that, how to do that using some abrakadabra:-) Regards, Pawe/l
At 08:40 16/09/2003 +0200, you wrote:
Hello!
In some special cases I need to set paths for input files directly from ConTeXt code not from config file. In manuals \setupexternalfigures is described. Is there any similar command for files that are inputed directly by \input, \typefile \processXMLfile (the last is the most interesting for me) and similar commands?
If there isn't any special command for that, how to do that using some abrakadabra:-)
you can set the directory (gebied in dutch) with: \setupsystem or pass --path to texexec 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 ------------------------------------------------------------------------- information: http://www.pragma-ade.com/roadmap.pdf documentation: http://www.pragma-ade.com/showcase.pdf -------------------------------------------------------------------------
Hello!
you can set the directory (gebied in dutch) with:
\setupsystem
or pass --path to texexec
Thanks a lot Hans! Although I can't still use \setupsystem properly (even with looking at core-code tricks), --path option seems to be the solution. I've solve processing XML files in this way. Typing (\typefile) and inputing (\input) files are still the quest. --path seems not to work with this commands or I do something wrong. I'll look closely into it. Regards, Pawe/l
At 17:37 17/09/2003 +0200, you wrote:
Hello!
you can set the directory (gebied in dutch) with:
\setupsystem
or pass --path to texexec
Thanks a lot Hans! Although I can't still use \setupsystem properly (even with looking at core-code tricks), --path option seems to be the solution. I've solve processing XML files in this way. Typing (\typefile) and inputing (\input) files are still the quest. --path seems not to work with this commands or I do something wrong. I'll look closely into it.
another option is to use: \usepath[list of paths] \usesubpath[list of subpaths] 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 ------------------------------------------------------------------------- information: http://www.pragma-ade.com/roadmap.pdf documentation: http://www.pragma-ade.com/showcase.pdf -------------------------------------------------------------------------
Hi!
another option is to use:
\usepath[list of paths] \usesubpath[list of subpaths]
Thanks again! It works almost like --path option -- files included with \processXMLfile ARE included, but files included by \input (or \typefile) ARE NOT. Anyway I've solved the problem already. I described it below in case somebody have the same pain. I have to make a package for automatic conversion XML2PDF. I decide to use ConTeXt for it (neither XSLT nor xmltex, ..., are so suitable) and that is how our love began! The problem is that the package should be independent from kpathsea as far as possible. I mean searching paths for macros, fonts, encodings, ..., must be configurable internaly, without touching texmf.cnf and any other config files. There are three reasons: one is that my boss is unfortunately not interested in learnig/configuring/using TeX at all, second is that it must be portable and work with any(?) kpathsea installation with ConTeXt. The last but not least is that there isn't still miniTeX (really mini!) kpathsea distribution which may be very usefull in such situation... Of course it's possible to make this by cruel substraction of existing distributoion but... Anyway I wrote some perl-scripts, which solve kpathsea-like syntax in independent config file (which is nice training:-). Variables (i.e TEXINPUTS) defined in this small, external config and are either temporarly exported to (nested) environment or rewriten to generated context code (into \setupexternalfigures[directory=...], \usepath[...] and so on). Script traverse a tree of XML documents and generate context-codes which are compiled directly to PDF. It is still experimental and not best solution, but works ok. Meybe somebody have made this voyage already? Regards, Pawe/l
At 12:18 18/09/2003 +0200, you wrote:
I have to make a package for automatic conversion XML2PDF. I decide to use ConTeXt for it (neither XSLT nor xmltex, ..., are so suitable) and that is how our love began! The problem is that the package should be independent from kpathsea as far as possible. I mean searching paths for macros, fonts, encodings, ..., must be configurable internaly, without touching texmf.cnf and any other config files. There are three reasons: one is that my boss is unfortunately not interested in learnig/configuring/using TeX at all, second is that it must be portable and work with any(?) kpathsea installation with ConTeXt. The last but not least is that there isn't still miniTeX (really mini!) kpathsea distribution which may be very usefull in such situation..
let's tell you a little secret: www.pragma-ade.com/context/cont-bas.tex www.pragma-ade.com/context/setup www.pragma-ade.com/context/setuptex.bat (also, the example framework --work in progress-- permits you to run multiple trees in parallel and make choices depending on a task) 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 ------------------------------------------------------------------------- information: http://www.pragma-ade.com/roadmap.pdf documentation: http://www.pragma-ade.com/showcase.pdf -------------------------------------------------------------------------
Hans Hagen said this at Thu, 18 Sep 2003 14:46:56 +0200:
let's tell you a little secret:
www.pragma-ade.com/context/cont-bas.tex
Yeah, I just noticed cont-bas.zip just yesterday.... how long has that been there? For a while I've been asking myself what would the minimal texmf tree for context look like, and of course Hans already has the answer. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay atl@comp.lancs.ac.uk Computing Dept, Lancaster University +44(0)1524/594.537 Lancaster, LA1 4YR, UK Fax:+44(0)1524/593.608 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
At 14:30 18/09/2003 +0100, you wrote:
Hans Hagen said this at Thu, 18 Sep 2003 14:46:56 +0200:
let's tell you a little secret:
www.pragma-ade.com/context/cont-bas.tex
Yeah, I just noticed cont-bas.zip just yesterday.... how long has that been there?
For a while I've been asking myself what would the minimal texmf tree for context look like, and of course Hans already has the answer.
for a while, since i need it so set up minimal trees; in addition i have a script that takes cont-bas, as well as cont-tfm and generates all the fonts and so; resulting in some 50 meg tree which has all you need; here i use: tex/texmf -> current tex live tex/texmf-local -> latest context tex/texmf-fonts -> extra fonts and metrics tex/texmf-project -> project specific files tex/texmf-mswin -> mem/pool/bin tex/texmf-darwin -> mem/pool/bin tex/texmf-linux -> mem/pool/bin and for specific projects: tex/texmf -> minimal tree .... the advantage of the small tree is that it runs much faster (i will put a minimal tree on the server some day soon so that users who want can sync with it) 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 ------------------------------------------------------------------------- information: http://www.pragma-ade.com/roadmap.pdf documentation: http://www.pragma-ade.com/showcase.pdf -------------------------------------------------------------------------
www.pragma-ade.com/context/cont-bas.tex www.pragma-ade.com/context/setup www.pragma-ade.com/context/setuptex.bat
(also, the example framework --work in progress-- permits you to run multiple trees in parallel and make choices depending on a task)
This secret looks nice! I'll look into it closely. Thanks a lot! Pawe/l
Hi all! Some days ago I asked a question about setting paths to inputed files. Now I see the question may be missunderstood. Sorry for that. I'll try to repeat in some other way. I need to set directories for included files. For some reason I don't want to say \input ./my-dir/my-file I'd rather setup directory ./my-dir in the begining of the project and than make it possible to say just \input my-file or \type my-file or even \processXMLfile{my-file} % most important for me There is a commmand \setupexternalfigures[directory={./my-dir}] which allow to do that for external figures. Is it also possible to set directory for included TeXt-files? There is also \setupsystem command; is it a good trace (I didn't find any example of usage)? Give me some hints, please. Thanks, Pawe/l
participants (3)
-
Adam Lindsay -
Hans Hagen -
Pawel Jackowski na Onet