[XeTeX] Output file removed; Output written on...

[Peter Dyballa]

Am 28.11.2007 um 16:05 schrieb maxwell:

> Now that I think of it, why was it necessary for me to use the
> ExternalLocation?  Why couldn't xdvipdfmx find the font (which was in
> /usr/share/fonts/local/)?  Is that not a standard location, and if  
> not,
> where should I put it?  Or is there an environment variable that gives
> *additional* locations?  I tried TEXFONTS (I think it was), without
> success.

TEXFONTS is of no help here, because it points to TFM files.  
Xdvipdfmx uses libfontconfig (fc-list, fc-cache). Its configure file 
(s) tell(s) where to look for fonts. 'man fc-list' etc. can provide  
necessary information for your system.

>
> I'm not even sure where xdvipdfmx comes from; I guess it came with the
> TeXLive distribution of xetex.  I have an executable of xdvipdfmx, but
> there doesn't seem to be any documentation--no man page, for instance.
> The --help parameter talks about a "font map file name", but I  
> don't know
> what that's supposed to look like, nor where it should reside.  I  
> don't
> seem to have one by the default name (t1fonts.map) in any obvious
> location.


Xdvipdfmx is a twice extended version of dvipdfm: first it learned to  
handle Unicode, CJK scripts, and their large fonts as dvipdfmx, then  
it learned to convert XeTeX's XDV output file to PDF and take the  
fonts from the system (libfontconfig). Coming from dvipdfm it can  
also handle the TeX font system and therefore needs a MAP file  
(dvipdfm.map) that translates a TeX font name to a file name on disk.  
Updmap or updmap-sys produces this MAP file from MAP file fragments,  
which it manages too.

In summer 2003 dvipdfmx was presented to TUG. More information maybe  
here: http://project.ktug.or.kr/dvipdfmx/, http:// 
gaspra.kettering.edu/dvipdfm/. You can also invoke 'texdoc dvipdfm'.

--
Greetings

   Pete

We also sponsor National Invisible Chronic Illness Awareness Week  
annually in September.
Join the millions