[OS X TeX] Re: OpenType fonts
Thomas A. Schmitz
thomas.schmitz at uni-bonn.de
Mon Oct 17 13:14:31 EDT 2005
thanks for your suggestion, but like you suspected: it doesn't help.
TeX finds every file it needs, except for the otf:
kdebug:fopen(testfont.pdf, wb) => 0xa000dcec
updmap/pdftex.map, rb) => 0xa000dd9c
pdftex.mapkdebug:fclose(0xa000dd9c) => 0
KERN-LIGA-DLIG-ONUM-ACaslonPro-Regular.vf, rb) => 0xa000dd9c
KERN-LIGA-DLIG-ONUM-ACaslonPro-Regular--base.tfm, rb) => 0xa000ddf4
kdebug:fclose(0xa000ddf4) => 0
kdebug:fclose(0xa000dd9c) => 0
cm/cmtt10.pfb, rb) => 0xa000dd9c
cmtt10.pfb>kdebug:fclose(0xa000dd9c) => 0
a_6cirpq.enc, rb) => 0xa000dd9c
(0xa000dd9c) => 0
Error: pdfetex (file ACaslonPro-Regular.otf): cannot open OpenType
font file fo
==> Fatal error occurred, the output PDF file is not finished!
Pretty bizarre. So all we can say right now: the path given for .otf
in kpsewhich is not used by pdf(e)tex. I'm still puzzled.
On Oct 17, 2005, at 2:00 AM, Peter Dyballa wrote:
> I have no real answer, but since some time you can debug how the TeX
> programmes and companions work:
> pdfetex -kpathsea-debug 4 testfont
> With the value 4 libkpathsea will make pdfetex report all files it
> opens. Well, it does not show where pdfetex does *not* search ...
> its addition be an improvement?
> The numbers to -kpathsea-debug are actually bit masks so you can add a
> few of them and pass these as the sum of them all to -kpathsea-debug.
> The documentation can be read in 'texdoc kpathsea' beginning at
> page 23
> Some TeX companions use a different scheme, but that's then documented
> in the manual page or in <companion> --help.
------------------------- Info --------------------------
Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
& FAQ: http://latex.yauh.de/faq/
TeX FAQ: http://www.tex.ac.uk/faq
List Archive: http://tug.org/pipermail/macostex-archives/
More information about the MacOSX-TeX