[XeTeX] Could This Be a Problem?

[Herbert Schulz]

On Jul 14, 2005, at 9:17 AM, Jonathan Kew wrote:

> On 14 Jul 2005, at 3:03 pm, Herbert Schulz wrote:
>
>
>> Howdy,
>>
>> Files I created using xelatex and the Zapfino font (An invitation!  
>> Lovely font for doing that sort of thing.) leave the following in  
>> the system.log:
>>
>> Jul 14 07:49:29 HSPBG4 xdv2pdf: WARNING: Type1 font data returned  
>> by OFAStreamPSDownload isn't in the correct format required by the  
>> Adobe Type 1 Font Format specification.
>> Jul 14 07:49:29 HSPBG4 xdv2pdf: WARNING: Type1 font data returned  
>> by OFAStreamPSDownload isn't in the correct format required by the  
>> Adobe Type 1 Font Format specification.
>> Jul 14 07:49:29 HSPBG4 xdv2pdf: WARNING: Type1 font data returned  
>> by OFAStreamPSDownload isn't in the correct format required by the  
>> Adobe Type 1 Font Format specification.
>> Jul 14 07:49:48 HSPBG4 xdv2pdf: WARNING: Type1 font data returned  
>> by OFAStreamPSDownload isn't in the correct format required by the  
>> Adobe Type 1 Font Format specification.
>> Jul 14 07:49:48 HSPBG4 xdv2pdf: WARNING: Type1 font data returned  
>> by OFAStreamPSDownload isn't in the correct format required by the  
>> Adobe Type 1 Font Format specification.
>> Jul 14 07:49:48 HSPBG4 xdv2pdf: WARNING: Type1 font data returned  
>> by OFAStreamPSDownload isn't in the correct format required by the  
>> Adobe Type 1 Font Format specification.
>>
>
> Are you sure it's Zapfino that's triggering this? There's an issue  
> with old .pfb fonts under Tiger; that's what normally generates  
> this warning, though the PDFs appear to display correctly. I'm  
> still trying to find out whether there really is something XeTeX is  
> doing wrong, or if it's a CoreGraphics/ATS problem. (Under Panther,  
> the warning messages didn't occur.)
>
> Incidentally, if you run xetex from the Terminal rather than  
> TeXShop (or similar), you'll see the warnings right there, without  
> having to go check the system log file.
>

Howdy,

Yeah... as usual you're correct. The file using Zapfino isn't giving  
rise to those errors. Those lines were generated by compiling the  
following test file which has maths:

%!TEX TS-program = xelatex
%!TEX encoding = UTF-8 Unicode
\documentclass{article}
\usepackage{amsmath}
\usepackage{fontspec} % 1.8 with definition of \colon commented out
\usepackage{xunicode}
\defaultfontfeatures{Mapping=tex-text}
\setromanfont[Numbers=Lining,Scale=1.05]{Hoefler Text}
\begin{document}
Here is an Upper Case Gamma: \(\Gamma\)!

Here are some more: \(\{\), \(\}\), \(\land\), \(\lor\),
\(\aleph\), and \(\neg\).

How about math accents: \(\dot x = \ddot x\).
\end{document}

so it's probably coming from the CM math fonts.

>
>> I don't know if this is a problem or in any way related to the  
>> large time delays I see in displaying the generated pdf. I even  
>> get incorrect glyphs displayed if I recompile quickly without  
>> deleting the old pdf, etc., first.
>>
>
> Oh? That's a new one to me; I'll look out for it.
>
> JK
>

Recompiling this file in TeXShop quickly without deleting the  
previously generated pdf shows a very slow incremental build of the  
new pdf in the display. I think it's Tigerrrr! The first compile  
takes quite a while to show up so maybe the same thing is happening  
there but the display doesn't come up until it's complete.

Good Luck,

Herb Schulz
(herbs at wideopenwest.com)