On a Windows Vista-based or Windows Server 2008-based computer, you have a printer on which some device fonts are installed. On the computer, you change some fonts in the font substitution table of the printer from TrueType fonts to the printer’s device fonts. However, you cannot change the settings back to the original TrueType fonts. Therefore, if you have a character that does not print correctly by using the device fonts, the correct output for that character cannot be obtained.

Consider the following scenario:

• You print some documents.
• The printer driver is based on Microsoft Universal Printer Driver (Unidrv).
• The rendering occurs on a computer that is running an x64 version of Windows Server 2008, of Windows Vista, or of Windows Server 2003.
• The printer driver includes some font metrics data in its resource DLLs. The data is in formats compatible with versions of Windows earlier than Windows 2000. (This situation usually occurs in drivers for old nine-pin printers.)
• Text strings that are output to the printer are formatted in a device font.

In this scenario, certain printer drivers may print the text characters by using incorrect ASCII character codes. Therefore, the output may be rendered by using incorrect fonts. Additionally, text that is formatted in bold or italic fonts may be rendered differently on a 32-bit platform than on a 64-bit platform. In this case, the 32-bit platform output is correct.

Notes:

• This problem occurs only on x64 versions of Windows Server 2008, of Windows Vista, and of Windows Server 2003. It does not occur on x86-based versions of these operating systems.
• Documents are rendered before they are printed. This problem occurs on the computer on which rendering is performed. Rendering may occur on the client or on the print server, depending on several factors specific to each configuration. Therefore, to understand whether the hotfix that is described in this article is applicable, you must consider the platform type (32-bit or 64-bit) for the client and for the print server.

A computer that is running Windows Server 2003, Windows Vista, or Windows Server 2008 may restart unexpectedly. Additionally, you may receive the following Stop error message:

Stop 0×00000050 (parameter1, 00000000, parameter3, 00000000)
PAGE_FAULT_IN_NONPAGED_AREA

Notes

• The parameters in this Stop error message vary, depending on the configuration of the computer.
• Not all “0×00000050″ Stop error messages are caused by this problem.

This problem may occur if the computer uses some OpenType fonts that are provided by printer drivers.

Consider the following scenario:

• You are running a Windows XP-based computer.
• You create an End User Defined Character (EUDC) font.
• You deploy the EUDC font to a Windows Vista-based computer or to a Windows Server 2008-based computer.

In this scenario, you cannot enter the EUDC characters by using the Pinyin (phonetic) Input Method Editor (IME) or the Changjie IME.

This issue also occurs if you upgrade a Windows XP-based computer to Windows Vista.

Before you install certain language interface packs (LIPs) for Windows Vista and for the 2007 Microsoft Office system, you must first preinstall a new font update. The LIPs that require the preinstallation of this new font update are as follows:

• Georgian
• Malayalam
• Kannada
• Punjabi
• Telugu
• Armenian

Please be aware that the following SKUs are affected. Therefore, you must preinstall the font update before you install the previously-mentioned LIPs for the following SKUs.

The affected Vista SKUs are as follows:

• Windows Vista Starter
• Windows Vista Home Basic
• Windows Vista Home Premium
• Windows Vista Ultimate
• Windows Vista Business
• Windows Vista Enterprise

The affected 2007 Microsoft Office system SKUs are as follows:

• Microsoft Office Personal 2007
• Microsoft Office Standard 2007
• Microsoft Office Professional 2007
• Microsoft Office Ultimate 2007
• Microsoft Office Professional Plus 2007
• Microsoft Office Enterprise 2007

Consider the following scenario:

• You are running a Windows XP-based computer.
• You create an End User Defined Character (EUDC) font.
• You deploy the EUDC font to a Windows Vista-based computer or to a Windows Server 2008-based computer.

In this scenario, you cannot enter the EUDC characters by using the Pinyin (phonetic) Input Method Editor (IME) or the Changjie IME.

This issue also occurs if you upgrade a Windows XP-based computer to Windows Vista.

On a Windows Vista-based computer that has a 1280 by 800 screen resolution, you reset the screen font size to the Larger scale (120 DPI) setting. However, when you restart the computer, you see that the logon screen is now clipped. Therefore, you have to scroll down the logon screen to enter your password.

Note: This issue does not occur when you use the Default scale (96 DPI) setting.

On a Windows Vista-based computer, you turn off the User Account Control (UAC) feature. However, if you log on to the computer as a regular user, and then you try to install a font, the operation fails without any error message.

During the installation process, a circle appears around the pointer, and then it disappears. At the same time, the CPU usage increases to 100 percent for a while. The operation seems to finish successfully. However, when you check Fonts in Control Panel, the font that you tried to install does not exist.

Type 1 fonts installed in the Fonts control panel on Windows XP Professional x64 or Windows Vista x64 do not list in the font menus of Adobe Creative Suite 2 applications.

Fonts display as expected in other Windows applications (for example,Character Map, Wordpad).

When you print a document that contains both vertical fonts and non-vertical fonts in Windows Vista, the document does not print correctly on a PostScript printer. For example, some printed characters may be broken up.

Note: A vertical font is designated with an “at” character (@) as the first character of its name. Vertical fonts are typically used on Asian systems.