Glyph Problems With Automatic Type 1 To TrueType Font Converte

Last reviewed: August 26, 1996
Article ID: Q131841
The information in this article applies to:
  • Microsoft Windows NT Workstation version 3.5
  • Microsoft Windows NT Server version 3.5

SYMPTOMS

The Windows NT 3.5 automatic Type 1 to TrueType font converter exhibits the following problems:

  • It is unable to handle repeated encoding.

    If a glyph appears in more than one place in the encoding vector, then one occurrence of the glyph is lost.

  • It is unable to handle character code zero.
  • It overwrites glyph character code 173 with glyph character code 45.

    The Windows character codes 45 and 173 are hyphens "-". The converter copies character code 45 to character code 173.

RESOLUTION

To correct this problem, install the latest U.S. Service Pack for Windows NT version 3.5 or upgrade to Windows NT 3.51.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.5. This problem has been corrected in the latest U.S. Service Pack for Windows NT version 3.5. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

This problem was also corrected in Windows NT version 3.51.

MORE INFORMATION

TrueType and Adobe Type 1 fonts are outline fonts, containing glyph shapes that are described by their outlines. A glyph outline consists of a series of contours that define the boundaries of the glyph. Some glyphs are simple, such as most letters and punctuation marks, but some can be quite complex. For example, a company logo with graphics and text might be encoded in a font as a single glyph.


KBCategory: kbdisplay kbprint kbbug3.50 kbfix3.50.sp3 kbfix3.51
KBSubcategory: ntprint NTSrvWkst
Additional reference words: prodnt 3.50 ttf ansi


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: August 26, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.