[tex-live] TEXINPUTS problem

[Gerben Wierda]

Here is an issue about kpathsea. Question at the end.

Begin forwarded message:

> From: Jonathan Kew <jonathan_kew at sil.org>
> Date: October 15, 2004 14:51:28 CEST
> To: "TeX on Mac OS X Mailing List" <MacOSX-TeX at email.esm.psu.edu>
> Subject: Re: [OS X TeX] Re: Context problem
> Reply-To: "TeX on Mac OS X Mailing List" <MacOSX-TeX at email.esm.psu.edu>
>
> On 15 Oct 2004, at 1:05 pm, Ross Moore wrote:
>
>> Hi Jonathan, and Bruno
>>
>> On 15/10/2004, at 8:13 PM, Jonathan Kew wrote:
>>
>>> On 15 Oct 2004, at 10:50 am, Bruno Voisin wrote:
>>>> PS: Some technical details. With TL 2004, during creation of 
>>>> pdfLaTeX you'll get:
>>>>
>>>>> running `etex -ini   -jobname=latex -progname=latex *latex.ini' ...
>>>>> This is pdfeTeX, Version 3.141592-1.20a-2.2 (Web2C 7.5.3) (INITEX)
>>>>> ...
>>>>> (/usr/local/teTeX/share/texmf.tetex/tex/generic/babel/hyphen.cfg
>>>>> ...
>>>
>>>> On the other hand during creation of XeLaTeX you'll get:
>>>>
>>>>> running `xetex -ini   -jobname=xelatex -progname=xelatex 
>>>>> *xelatex.ini' ...
>>>>> This is XeTeX, Version 3.14159-2.1-0.871 (Web2C 7.5.2) (INITEX)
>>>>> ...
>>>>> (/usr/local/teTeX/share/texmf.tetex/tex/cslatex/hyphen.cfg
>>>>> ...
>>>
>>> There's the problem: searching for hyphen.cfg, xetex is finding the 
>>> file in tex/cslatex in preference to the one in tex/generic/babel.
>>
>> OK, maybe this is a symptom of a feature that I call the "matrix 
>> transpose" problem.
>
> Maybe; or maybe it's simply because the order of kpathsearch 
> subdirectory searching at any given level is unspecified (according to 
> the docs I've seen); or maybe the algorithms used in kpathsearch have 
> changed in TeXLive 2004?
>
> In any case, it can probably be fixed by providing appropriate 
> TEXINPUTS.xetex and TEXINPUTS.xelatex entries (look at the 
> pdftex/pdflatex entries for inspiration) in texmf.cnf. In the absence 
> of program-specific entries, it will be using a default TEXINPUTS that 
> apparently allows the cslatex stuff to be found ahead of 
> generic/babel, but more specific paths should correct this.
>
> Perhaps that's enough of a clue for someone with TL2004 installed to 
> get things working?

The texmf.cnf made from texmf.in has this:

> % TEXINPUTS is for TeX input files -- i.e., anything to be found by 
> \input
> % or \openin, including .sty, .eps, etc.
>
> % Plain TeX.  Have the command tex check all directories as a last
> % resort, we may have plain-compatible stuff anywhere.
> TEXINPUTS.tex = .;$TEXMF/tex/{plain,generic,}//
>
> % pdfTeX.  This form of the input paths is borrowed from teTeX.  A 
> certain
> % variant of TDS is assumed here, unaffected by the build variables.
> TEXINPUTS.pdfcslatex = 
> .;$TEXMF/{pdftex,tex}/{cslatex,csplain,latex,generic,}//
> TEXINPUTS.pdfcsplain = .;$TEXMF/{pdftex,tex}/{csplain,plain,generic,}//
> TEXINPUTS.pdfjadetex = .;$TEXMF/{pdftex,tex}/{jadetex,plain,generic,}//
> TEXINPUTS.pdflatex = .;$TEXMF/{pdftex,tex}/{latex,generic,}//
> TEXINPUTS.pdfmex   = .;$TEXMF/{pdftex,tex}/{mex,plain,generic,}//
> TEXINPUTS.pdftex   = .;$TEXMF/{pdftex,tex}/{plain,generic,}//
> TEXINPUTS.pdfamstex = .;$TEXMF/{pdftex,tex}/{amstex,plain,generic,}//
> % The pdftexinfo entry is obsolete.
> TEXINPUTS.pdftexinfo = .;$TEXMF/{pdftex,tex}/{texinfo,plain,generic,}//
>
> % pdfeTeX.
> TEXINPUTS.pdfelatex = 
> .;$TEXMF/{pdfetex,pdftex,etex,tex}/{latex,generic,}//
> TEXINPUTS.pdfetex   = 
> .;$TEXMF/{pdfetex,pdftex,etex,tex}/{plain,generic,}//
>
> % pdfxTeX.
> TEXINPUTS.pdfxlatex = 
> .;$TEXMF/{pdfxtex,pdftex,etex,tex}/{latex,generic,}//
> TEXINPUTS.pdfxtex   = 
> .;$TEXMF/{pdfxtex,pdftex,etex,tex}/{plain,generic,}//
>
> % Earlier entries override later ones, so put this last.
> TEXINPUTS = .;$TEXMF/tex/{$progname,generic,}//

Given that, I cannot figure out why in the case of progname = xelatex 
it will find stuff in cslatex before generic.

Can someone explain this to me?

G