>> Does compilation of this small plain TeX test document
>>
>> ```
>> \font\lh = latt1095
>> \lh ^^c1
>> \bye
>> ```
>>
>> with `xetex` actually work?
>
> Since this short file didn't run,
Well, this explains what's going on.
> I will run the test file. But since you suggested this problem, I
> decided to check xetex and xdvipdfmx:
>
> carl@carls-mbp-2 build % which xetex
>
> /Library/TeX/texbin/xetex
>
> carl@carls-mbp-2 build % which xdvipdfmx
>
> /opt/local/bin/xdvipdfmx
Ouch. You have two TeX installations in your path: MacTeX (either
installed directly or via homebrew) and 'texlive-xxx' packages from
MacPorts, and the former is apparently missing XeTeX support (for
whatever reason) since the `xdvipdfmx` binary is missing. You have to
decide which one to use. Given that you are mostly relying on
MacPorts it's probably simpler to use MacPorts binaries.
If you don't want delete the non-MacPorts TeX installation you should
separate it. The simplest solution is probably to remove the symbolic
link `/Library/TeX/texbin` completely (the actual MacTeX tree is
`/usr/local/texlive/<year>` for homebrew, too) or to remove
`/Library/TeX/texbin` from your PATH environment variable. This makes
your MacPort's 'texlive' package the default.
[Note that I'm not a real Mac user, so please take my words with
caution – I'm mostly relying on internet information.]
> I thought it might be a good idea to just run the KPATHSEA_DEBUG on
> the test file.
Thanks, but right now this is not necessary because the problem is
obvious.
> I've attached the compressed log file from your short TeX file run
> through xetex.
Note that the attached archive is broken (and it doesn't use any
compression). What about simply using `gzip` to compress single files
in the future? Alternatives are `xz`, `bzip2`, or similar programs.
Werner
