[XeTeX] Strange problem with 0.996 and 0.9995 xetex and File Names.

[Herbert Schulz]

On Sep 5, 2009, at 9:55 AM, Fr. Michael Gilmary wrote:

> Herbert Schulz wrote:
>
>>
>> Howdy,
>>
>> With the file name `test II.tex' I have no problem; it's with the  
>> file name `Summary II.tex' I have a problem. Please don't ask why--- 
>> if I knew I'd understand it. Hmmm... Just tried `Summary III.tex'  
>> and got the internal * asking for commands. This just gets stranger  
>> and stranger.
>
>
>
> Well now, if I use what you suggest, `Summary II.tex', then TeXShop  
> runs it fine (on bash, I think, as it is the default shell for me)  
> --- and from the terminal, bash & ksh work, but not tcsh or zsh!  I  
> can run `test II.tex' no problem, but get the message in tcsh and  
> zsh, `Summary II.tex' gets:
>
>
>> ! I can't find file `"Summary II.texSELFAUTOPARENT"'.
>> <*> "Summary II.tex"SELFAUTOPARENT
>>                                  (Press Enter to retry, or Control- 
>> D to exit)
>> Please type another input file name: ^D
>> ! Emergency stop.
>> <*> "Summary II.tex"SELFAUTOPARENT
>
> (Also, I use auto-completion at the command line and the shell  
> inserts the \<sp> automatically. )
>
> What's your default shell for TeXShop (I suppose what loads with  
> your .profile or some other dot file)? Maybe SnowLeopard changed it?
>

Howdy,

I believe the default shell used by the internal and xe(la)tex engines  
supplied with TeXShop uses the tcsh. However, my default shell in  
Terminal is bash and the problem occurs in both TeXShop and Terminal  
for me.

Executing

$ echo Summary\ II.tex | od -x
0000000      7553    6d6d    7261    2079    4949    742e    7865     
000a
0000017

where the File name was generated by bash from tab completion seems to  
show that the space character that is giving me trouble (but in  
combination with the two characters after it!?) is just the regular  
<SPACE>.

I still think it's strange but interesting that position of the  
<SPACE> in the string makes a difference as well as how long the  
string is. E.g., changing the file name to `Summar II.tex' or `Summary  
IIII.tex' gives no problem while `Summary III.tex' gives me a  
different problem where xelatex drops into internal TeX processor and  
gives me the * prompt looking for input.

Is this somehow related to a byte ordering?

Good Luck,

Herb Schulz
(herbs at wideopenwest dot com)