Thanks for this clarification Dov. This simplifies things a great deal in that it implies that for any PS or PDF file that is destined to be sent to a high quality printing service bureau one can assume that allowing temporary font substitution in FM will not cause problems with final output having the correct font (since their devices will have Zapf-Dingbats installed). Or is that too optimistic a reading? Must the PS or PDF file be produced with that font available to FM on the machine producing the PS of PDF file? Craig From: isaacs at adobe.com To: framers at lists.frameusers.com Date: Wed, 23 Jan 2013 03:24:20 -0800 Subject: RE: The "Zapfdingbats" Font Family is not available. (Was: Updating older versions of Adobe fonts? Slightly off-topic, but related in a way!)
To be very clear, Adobe has not shipped a copy of Zapf Dingbats with FrameMaker since FrameMaker 5.5.6 if I recall correctly. However, in fact, every printer with Adobe PostScript 3 still ships with a host-installable Type 1 (both for Windows and Macintosh) versions of Zapf Dingbats. The real issue appears to be not whether Adobe ships this font under what circumstances, but rather, whether the users install the font (assuming they have use of an Adobe PostScript 3 device) and a likely bug/omission in FrameMaker by which a font substitution is made without making a character remapping to Unicode at the same time. - Dov -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.frameusers.com/pipermail/framers/attachments/20130123/0f148bb2/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 871 bytes Desc: not available URL: <http://lists.frameusers.com/pipermail/framers/attachments/20130123/0f148bb2/attachment.png>
