Hello,

On Sat, 26 Jul 2014 11:01:15 +0200, Hans Hagen <pra...@wxs.nl> wrote:

Hi,

There is a new experimental feature (one of the side effects of
discussions with Alan about bibliographies and using distributed files
in a project structure).

Say that you have this:

test1.tex : uses \component one/test2

one/test2.tex : uses \component two/test3

etc. There can be resources under one/two that test3 needs and one way
out is to add this path to the used paths. Doing that automatically can
result in side effects when multiple resources with the same name are used.

However, we now have a concept of the local job path, so when test2 is
read the jobfile: prefix will use path one, and when reading test3, that
prefix will trigger one/two usage.

very nice and handy feature, thanks for that.

Just a remark -
- there was a similar prefix "toppath:" introduced some time ago.

And - IIUC - "jobfile" refers to a dir rather than to a file, so wouldn't be better to call the 
prefix "jobdir:" or "jobpath:"?

Best regards,

Lukas


For this to work, one has to say:

\usepath[jobfile:]
\setupexternalfigures[directory=jobfile:]

To what extent this all works out well is to be tested.

Hans


--
Ing. Lukáš Procházka [mailto:l...@pontex.cz]
Pontex s. r. o.      [mailto:pon...@pontex.cz] [http://www.pontex.cz]
Bezová 1658
147 14 Praha 4

Tel: +420 241 096 751
Fax: +420 244 461 038

___________________________________________________________________________________
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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Reply via email to