Zapf Dingbat Fonts Map Incorrectly in Excel

Last reviewed: November 1, 1994
Article ID: Q71882

SUMMARY

The Zapf Dingbat printer fonts that are installed with PowerPoint will map incorrectly with the Zapf Dingbat screen fonts under Excel 3.00. If the Zapf Dingbat screen font is selected when you choose Font from the Format menu, the characters will appear correctly on the screen but will print in Times Roman or Courier. The opposite will occur if the Zapf Dingbat printer font is selected. The characters will appear as Times Roman or Courier on the screen but will print correctly. This problem did not occur under Excel 2.1x.

Microsoft is researching this problem and will post new information here as it becomes available.

MORE INFORMATION

To correct the mapping problem, the name of the printer font can be changed to more closely resemble the screen font name.

  1. Open the Control Panel in Windows.

  2. Select Printers, and choose Configure.

  3. Choose Setup and Fonts to access the Printer Font Installer.

  4. Select the first entry for ITC Zapf Dingbats SWA under Installed Fonts and choose Edit.

  5. Change the name of the font to ZapfDingbats (note that there are no spaces).

  6. Choose OK and then select the next Zapf Dingbat font.

  7. Continue this process until all the font names have been changed. Once all the printer font names have been changed, the printer and screen fonts will map as expected.


KBCategory: kbother
KBSubcategory:

Additional reference words: noupd


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: November 1, 1994
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.