Text After an Embedded Object May Be Printed with Some Blank Characters

When you print to a PostScript printer using fonts that are configured to download as soft fonts in the printer driver's Font Substitution table, text following an embedded object in a document may be printed incorrectly. Spaces may be substituted for some, but not all, characters.

For example, the text "This is a test" may be printed as "Thi_ i_ a te_t" (where underscores represent blank spaces.)

In some circumstances, with some soft fonts and some font sizes, the printer's soft font cache may be flushed when you print an embedded object that uses the same soft fonts as the text part of the document.

When this behavior occurs, the PostScript driver may reload only those characters in the soft font that are also used in the embedded object. In text following the embedded object, characters that are used in that object are printed normally; other characters are printed as white space. In the example above, the letters "T," "h," "i," "a," "e," and "t" are used in the preceding embedded object, but the letter "s" is not.

Windows NT Server or Workstation 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:

• http://www.microsoft.com/downloads/details.aspx?familyid=E396D059-E402-46EF-B095-A74399E25737&displaylang=en/ (http://www.microsoft.com/Windows/ServicePacks/) -or-
  
  
• 152734  (http://support.microsoft.com/kb/152734/EN-US/ ) how to obtain the latest windows nt 4.0 service pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:
The PostScript driver has been modified to reload soft fonts correctly following the printing of an embedded object.

Windows NT Server 4.0, Terminal Server Edition

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition.

This problem was first corrected in Windows NT Server 4.0 Service Pack 6 and Windows NT Server 4.0, Terminal Server Edition Service Pack 6.