[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[New search]
To: pdf@xxxxxxxxxxxxxxxxx, pdf-prepress-l@xxxxxxxxxxxxx, acrobat@xxxxxxxxxxxxx, CTP Pressroom <ctpp@xxxxxxxxxxxxxxx>, framers@xxxxxxxxxxxxxx, framers@xxxxxxxxx, Frame2Acrobat@xxxxxxxxxxx
Subject: Display Problems - ITC Zapf Dingbats & Windows 2000 - & a Workaround!
From: "Dov Isaacs" <isaacs@xxxxxxxxx>
Date: Mon, 27 Nov 2000 16:33:25 -0800
Sender: owner-framers@xxxxxxxxx
There appears to be a problem under Windows 2000 in which characters chosen from the ITC Zapf Dingbats font, one of the "base 35" PostScript Type 1 fonts, display in the TrueType WingDings font on the screen, but print OK to PostScript printers and generate correct PDF files. This affects most, but not all, applications. These applications in which the problem occurs appears to include all the applications which use Windows 2000's font rendering services as opposed to applications which internally control their own fonts. The applications affected include Microsoft Office, WordPerfect Office, Lotus Smartsuite, and FrameMaker, amongst others. If you have ITC Zapf Dingbats installed under Windows 2000 and correct characters both display and print from any of the above applications (including WordPad) for all characters formatted in ITC Zapf Dingbats, ignore the rest of this email. You have a version of ITC Zapf Dingbats installed that has a "correct" .PFM (PostScript Font Metrics) file. Applications NOT affected include Adobe Illustrator, Adobe Photoshop, Adobe Acrobat, and Adobe InDesign. Adobe is investigating the problem and a possible solution. In the interim, I recommend the following workaround that so far appears to work without any problems. Acrobat 4.0x and Acrobat Reader 4.0x include their own copy of the ITC Zapf Dingbat font. The .PFM file in Acrobat for ITC Zapf Dingbats seems to "fix" the problem for the system. Use the following procedure to use that PFM file instead of that currently used by the system: (0) Logon with a userid with Administrator rights. (1) Save (to a safe location) and then delete the ZD______.PFM file in PSFONTS\PFM (if you have ATM) or in the WINNT\FONTS directory, otherwise. (2) Copy the ZD______.PFM file from the Resource\Font\PFM subdirectory of Acrobat 4.0x or Acrobat Reader 4.0x to the directory from which you just deleted the .PFM file. (3) Reboot. I would be interested in any feedback in terms of users who either: (a) Have NOT experienced the problem, but do have ITC Zapf Dingbats installed ... please let me know where and when you obtained the fonts and the file modification dates. (b) Are experiencing the problem and the fix works completely. (c) Are experiencing the problem and the fix either doesn't work or has side effects. Please respond to me directly, not to these lists. Thank you. - Dov PS: FrameMaker users -- the PFM file we are recommending for the workaround is NOT the infamous Windows NT Dingbats Fix font from 1997. That fixes the display problem, but does NOT print all characters correctly!!! ** To unsubscribe, send a message to majordomo@omsys.com ** ** with "unsubscribe framers" (no quotes) in the body. **