[XeTeX] xelatex not working

[Joshua Grauman]

Ok, so I got past the xkeyval problem, and have another one ;)

This is my error:

(/usr/local/teTeX/share/texmf-local/tex/xelatex/xkeyval/keyval.tex)))
fontspec.cfg loaded.
(/usr/local/teTeX/share/texmf-local/tex/xelatex/fontspec/fontspec.cfg))
(./Hebrew3.aux) [1] (./Hebrew3.aux) )
(null) -> Hebrew3.pdf
[1
** ERROR ** Unable to find TFM file "cmr10".


However, I have the file:

/usr/local/teTeX/share/texmf-dist/fonts/tfm/public/cm/cmr10.tfm

But, then again, I don't understand the TeX paths... Thanks again.

Josh

> Although not familiar at all with the TeX paths, I thought I'd at least
> throw in the clarification that I am not using TeX Live. The way I
> installed was to remove all traces of TeX on my Slackware 10.2 box, and
> then to install the latest version of teTeX 3.0. Then I had to upgrade
> fontconfig, then I installed XeTeX. I followed the "Quick Install" method
> for teTeX 3.0 which should be somewhat standard, I thought... Thanks again
> for all your work, don't know if this is helpful, but just in case...
>
> Josh
>
>> On 9 Aug 2006, at 5:36 pm, Ralf Stubner wrote:
>>
>>> Jonathan Kew <jonathan_kew at sil.org> writes:
>>>
>>>> However, I believe the precedence of DIST over LOCAL (where the xetex
>>>> additions currently end up) would still lead to the same problem.
>>>
>>> ACK. I just don't think it is very likely that DIST comes before LOCAL
>>> in the search order.
>>
>> It seems to be OK in the current TL source repository, but I'm sure
>> I've seen them the other way round in some distro or other; I
>> remember being surprised by it.
>>
>>>> Really, the main xkeyval in DIST needs to be updated.
>>>
>>> Indeed. And I assume that the next TeX Live will have an uptodate
>>> version.
>>
>> Currently, it's new enough for fontspec but not the latest from CTAN;
>> care to check that it gets updated?
>>
>>> Do you know to which extend package authors have been contacted about
>>> adding XeTeX support/detection to their packages?
>>
>> No, I don't. This is something I haven't yet had time and energy to
>> pursue, but it should certainly be done for whatever packages have
>> engine/driver dependencies. In some cases (maybe geometry? crop?)
>> that have been discussed on the list, other users may have done this.
>> I don't generally use these things personally, so I'm not likely to
>> run across the issues until someone reports a problem!
>>
>> JK
>>
>>
>> _______________________________________________
>> XeTeX mailing list
>> postmaster at tug.org
>> http://tug.org/mailman/listinfo/xetex
>>
> _______________________________________________
> XeTeX mailing list
> postmaster at tug.org
> http://tug.org/mailman/listinfo/xetex
>