[XeTeX] Finished testing Adobe OpenType Font Folio on the Mac

[William Adams]

On Jul 4, 2006, at 4:25 AM, Jonathan Kew wrote:

> I doubt the .xdv would show anything -- xetex is finding the font, or
> it would complain. Most likely xdv2pdf is somehow failing. You might
> want to run xetex -no-pdf and then xdv2pdf separately in Terminal, so
> you don't miss any messages (no crash log, I presume?).

No, everything seems to complete okay, it's just that there's no .pdf  
--- is there some temp location I could examine to see if the .pdf is  
there?

> Check console.log for any messages from Quartz, too; if it's not
> actually crashing, then I wonder if Quartz is somehow unhappy with
> that font.

Actually, this is happening on w32tex --- works fine on Mac OS X.

> Not much I can do to investigate it, though, as I don't
> have access to the Adobe collection. Anyone with an Adobe friend care
> to suggest that they donate a copy for testing purposes? ;)

Have you tried getting in touch with Thomas Phinney? David Lemon once  
suggested I do so for similar reasons. I'd think Adobe would be glad  
of such testing.

Does this mean that the balance of the information I've worked up is  
not useful?

(that Notre Dame LT Std, Pompeijana LT Std, Rusticana LT Std and  
Wiesbaden Swing LT Std set dingbats / borders / ornaments rather than  
text or that ITC Stone Sans Std, ITC Stone Serif Std, New Century  
Schoolbook LT Std, Times LT Std don't set capital letters, or in some  
instances numbers)

If there's any sort of output from dumperfuser or ttx which'd help  
I'd be glad to (did you get the name tables I'd sent you for the text/ 
border fonts?)

William

-- 
William Adams
senior graphic designer
Fry Communications



This email message and any files transmitted with it contain information
which is confidential and intended only for the addressee(s). If you are
not the intended recipient(s), any usage,  dissemination, disclosure, or
action taken in  reliance on it is prohibited.  The reliability of  this
method of communication cannot be guaranteed.  Email can be intercepted,
corrupted, delayed, incompletely transmitted, virus-laden,  or otherwise
affected during transmission. Reasonable steps have been taken to reduce
the risk of viruses, but we cannot accept liability for damage sustained
as a result of this message. If you have received this message in error,
please immediately delete it and all copies of it and notify the sender.