From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ConTeXt on Excursion: translations in the Garden
Date: Mon, 14 May 2007 22:46:20 -0400 (EDT) [thread overview]
Message-ID: <alpine.WNT.0.99.0705142235390.3152@nqvgln> (raw)
In-Reply-To: <20070510144429.GA17296@phare.normalesup.org>
On Thu, 10 May 2007, Arthur Reutenauer wrote:
>> I wasn't able to test my answer because I use myself a different file structure
>> for the beginners manual and never encountered this problem.
>
> I guess the problem is with \doiffileelse in ma-cb-setups.tex:
>
> # \doiffileelse{t-setup.tex}
> # {\usemodule[setup]} % third party t-setup.tex
> # {\usemodule[set-11]}
>
> As it is (without tweaking TEXINPUTS or installing t-setup.tex
> manually), t-setup.tex isn't found in the parent directory, so
> x-set-11.tex is loaded in its place.
Why is it done this way? Isn't t-setup always supposed to be
distributed with the sources. Why not simply
\environment t-setup
If a file is being used for only one project, it should be an
environment file. If it will be used in multiple projects, it should
be a module.
Wolfgang, do you think that t-setup.tex can be added as x-set-13.tex,
or maybe even overwrite x-set-11.tex? (I have not read it carefully to
understand what are the enhancements that it provides).
> How is \doiffileelse supposed to search for files exactly?
Try to open the file for reading. If the file can be read, then read
the file, else do the else part. The check for file etc is done using
TeX's \immediate\openin\scratchread \filename, so there is no
searching for parent directories. The \project and \environment macros
have to make some effort to read files in parent directories.
Aditya
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2007-05-15 2:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 17:42 Vit Zyka
2007-05-09 0:26 ` luigi scarso
2007-05-09 7:34 ` Hans Hagen
2007-05-09 9:55 ` Vit Zyka
2007-05-09 13:41 ` John R. Culleton
2007-05-09 14:26 ` luigi scarso
2007-05-09 6:09 ` Aditya Mahajan
2007-05-10 1:05 ` Zhichu Chen
2007-05-10 1:54 ` Arthur Reutenauer
2007-05-10 4:48 ` Zhichu Chen
2007-05-10 6:38 ` Wolfgang Schuster
2007-05-10 12:42 ` Arthur Reutenauer
2007-05-10 14:06 ` Wolfgang Schuster
2007-05-10 14:44 ` Arthur Reutenauer
2007-05-11 6:44 ` Zhichu Chen
2007-05-15 2:46 ` Aditya Mahajan [this message]
2007-05-15 19:51 ` Wolfgang Schuster
2007-05-15 20:41 ` Arthur Reutenauer
2007-05-15 22:45 ` Aditya Mahajan
2007-05-16 18:01 ` Wolfgang Schuster
2007-05-10 18:05 ` Renaud Aubin
2007-05-10 7:39 ` Taco Hoekwater
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=alpine.WNT.0.99.0705142235390.3152@nqvgln \
--to=adityam@umich.edu \
--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).