[dev-context] XeTeX and font-selection problems

Hans Hagen pragma at wxs.nl
Tue Sep 11 23:58:28 CEST 2007

Taco Hoekwater wrote:
> Hans Hagen wrote:
>>>   I guess it's time for the ConTeXt developers to start over that little
>>> discussion we had with the XeTeX developer(s) :-)
>> hm, we use batchmode to catch an non found font so that we can look 
>> further; i would not expect xetex to quit then
> You misunderstand, it is texexec that does the quitting.
> I've seen this before, but forgot about it. The problem is that
> whenever tex sees an error, it's return value changes from zero
> to non-zero. It has been like that since (at least) the emtex days,
> with higher return value numbers indicating ever more serious
> issues that were encountered.
> The immediate problem is that the non-zero return makes texexec
> think that xetex has failed completely. That is not true, nor is
> it xetex-specific.
> We should probably see if we (the tex developers) can reach an
> agreement about how to decide if a font exists without raising
> an error, but in the mean time it is maybe best to ignore return
> values from engines as long as the expected output file is
> there (or forget about the nice font trick).

tex.rb line 1933 :

                             ok = runtex(File.suffixed(if dummyfile || 
forcexml then rawbase else rawname end,jobsuffix))

if getvariable('engine') == "xetex" then
     ok = true

so, xetex runs are always valid now (at least till we have a solution)

                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl

More information about the dev-context mailing list