Re: [NTG-context] Re: reset \use[sub]path

2003-11-10 Thread Hans Hagen 
At 17:37 10/11/2003, you wrote:
Hi,

 From: Hans Hagen [EMAIL PROTECTED]
 \usesubpath[reset]
Hans, are you sure about that?
(\use*sub*path)
 Also without expected results. So what is wrong in the following
 code?

 \starttext
 \usesubpath[lofo1]
 \processXMLfilegrouped{aqq.xml}
 \usesubpath[reset]
try: \usepath[reset]
indeed reset only works for usepath

(has to do with the fact that any \usesubpath triggers extension of the 
path list)

Hans

___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] Re: reset \use[sub]path

2003-11-10 Thread Pawel Jackowski na Onet 
Problem: reset path

  Also without expected results. So what is wrong in the following
  code?
 

  \starttext
  \usesubpath[lofo1]
  \processXMLfilegrouped{aqq.xml}
  \usesubpath[reset]

 try: \usepath[reset]

I did so. I've noticed that 'reset' option works for \usepath only but I
still get the solution. Please consider the following example (attached). We
have './lofo1' and './lofo2' directories, each contains 'x.xml' file (the
same filename but different content). ConTeXt code is as following:

\starttext
 \usepath[lofo1]
 \processXMLfilegrouped{x.xml}

 \usepath[reset]

 \usepath[lofo2]
 \processXMLfilegrouped{x.xml}
\stoptext

In this case 'reset' option works probably OK, since \allinputpaths variable
IS redefined to \empty (lines 99 to 104 of core-job.tex). So I expect that
the first processed XML file should be './lofo1/x.xml' and the second --
'./lofo2/x.xml'. But './lofo1/x.xml' file is processed twice instead. What
construction should I use to process two or more XML files, which have the
same name but different localization? I'm aware that my problem is not
common but...

Thanks for Your help, Pawe/l


usepath.zip
Description: Binary data

[NTG-context] Re: reset \use[sub]path

2003-11-10 Thread Patrick Gundlach 
Hello again,

 I did so. I've noticed that 'reset' option works for \usepath only but I
 still get the solution. Please consider the following example
 (attached). 

OK, I had a close look at it and digged into deeper mechanisms of
path handling in ConTeXt.

ConTeXt stores the exact location of a file just by the filename.
Once you read x.xml, ConTeXt remembers where it is. You get a hint
when saying \tracefilestrue in your tex source. Next time you read
x.xml, ConTeXt looks into its internal macros (fn..x.xml in this
case) and reads the full path. And this is lofo1 in your case.


I don't have a solution for you. Sorry.

Patrick
-- 
You are your own rainbow!
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context