DOCERR: Clarification of the LOGFONT lfOutPrecision Field

Last reviewed: July 23, 1997
Article ID: Q90372
3.10 WINDOWS kbtoolkbtoolg kbdocerr

The information in this article applies to:

  • Microsoft Windows Software Development Kit (SDK) for Windows version 3.1

SUMMARY

In Windows 3.1, additional symbolic constants have been defined for use in the lfOutPrecison field of the LOGFONT data structure. One of the constants, OUT_TT_PRECIS, is documented incorrectly on page 101 of the Windows SDK "Programmer's Reference, Volume 2" manual, on page 309 of the "Programmer's Reference, Volume 3" manual, and in the online help.

The OUT_TT_PRECIS constant is incorrectly documented as follows:

   Specifying OUT_TT_PRECIS forces the font mapper to choose a
   TrueType font whenever the specified font name matches a device or
   raster font, even when there is no TrueType font with the same
   name.

This paragraph should read as follows:

   Specifying OUT_TT_PRECIS forces the font mapper to choose a
   TrueType font whenever the specified font name matches both a
   TrueType font and either a device or raster font.

MORE INFORMATION

The OUT_TT_PRECIS, OUT_RASTER_PRECIS, and OUT_DEVICE_PRECIS values are used by Windows only when a name collision occurs during font mapping. If more than one type of font exists with the same name and the application does not specify one of these values, the font mapper will pick one of them randomly. By using one of these values, the application can direct the font mapper to the font the application wants to use.


Additional reference words: 3.10 CreateFont CreateFontIndirect docerr
KBCategory: kbprg kbdocerr
KBSubcategory: GdiTt
Keywords : kb16bitonly


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: July 23, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.