ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk>
Subject: Re: components and figure search paths
Date: Wed, 10 May 2006 08:56:51 -0400	[thread overview]
Message-ID: <E1FdoFH-0006oK-Vw@approximate.corpus.cam.ac.uk> (raw)
In-Reply-To: Your message of "Wed, 10 May 2006 13:25:27 +0200." <4461CDA7.2090607@wxs.nl>

[-- Attachment #1: Type: text/plain, Size: 1829 bytes --]

>From Hans:
> untested extension: \currentcomponentpath

Thanks!

Is the idea to use \currentcomponentpath in the directory={...}?  I put
those three \defs into core-job.tex and remade the formats (cont-en:
ver: 2006.04.17 23:14 fmt: 2006.5.10).  But I couldn't figure out quite
how to use it.  The abc-1.eps figure, referred to in the component and
living in its directory, isn't found automatically though maybe I need
to use \currentcomponentpath explicitly?

[Meanwhile I'm using a workaround that Mojca suggested offlist: by hand
put the relative component path in the directory={...}, which is mostly
fine as I don't change the relative directory structure as much as I
change the root.]

But back to \currentcomponentpath.  I put \show\currentcomponentpath in
the component chap/1/c_ch1.tex to see what was going on.  If I
understand right, your intention is that \currentcomponentpath would be
chap/1 inside chap/1/c_ch1.tex.  But it ends up as "..".  Here are the
relevant lines from the texexec log:

$ texexec onebook
systems         : begin file onebook at line 1
systems         : begin file project_books at line 2
(./project_books.tex
systems         : begin file env_books at line 3
(./env_books.tex)
systems         : end file env_books at line 3
)
systems         : end file project_books at line 2
systems         : begin file chap/1/c_ch1 at line 3
(./chap/1/c_ch1.tex
> \currentcomponentpath=macro:
->..
l.3 \show\currentcomponentpath
                              
? 
figures         : figure abc-1 can not be found
floatblocks     : 1 placed
)
systems         : end file chap/1/c_ch1 at line 3
[1.1]
systems         : end file onebook at line 4
 )

And here is a .tgz file with all of these files in this structure:

./chap/1/abc-1.eps
./chap/1/c_ch1.tex
./project_books.tex
./env_books.tex
./onebook.tex


[-- Attachment #2: component example --]
[-- Type: application/x-gtar, Size: 728 bytes --]

[-- Attachment #3: Type: text/plain, Size: 139 bytes --]

_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

  reply	other threads:[~2006-05-10 12:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-10  2:46 Sanjoy Mahajan
2006-05-10 11:25 ` Hans Hagen
2006-05-10 12:56   ` Sanjoy Mahajan [this message]
2006-05-10 13:31     ` Hans Hagen
2006-05-10 14:17       ` Sanjoy Mahajan
2006-05-10 14:38         ` Hans Hagen
2006-05-10 15:09           ` Sanjoy Mahajan
2006-05-10 15:13           ` David Arnold
2006-05-11  4:29             ` Sanjoy Mahajan
2006-05-11  5:21               ` Aditya Mahajan

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=E1FdoFH-0006oK-Vw@approximate.corpus.cam.ac.uk \
    --to=sanjoy@mrao.cam.ac.uk \
    --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).