The information in this article applies to:
SUMMARY
In your applications, you should use Windows fonts that are likely to be
installed on your users' machines. If your application uses fonts other
than the ones provided with FoxPro, limit those fonts to the ones found in
default Windows installations.
MORE INFORMATIONFonts Installed in Windows 3.0Fonts Installed in Windows 3.1Symptoms When a Font Is Not AvailableIf a font specified in your FoxPro application is not available, Windows uses font mapping to substitute the most similar available font. Depending on the substitution font used, text may be off-center, too small, or too large. In rare circumstances, it may even be unreadable, as is the case when the font mapper chooses a specialty font such as Symbol as the substitution font.Fonts Included with FoxProFoxPro installs FoxFont and FoxPro Window Font in Windows 3.0. In Windows 3.1, it also installs the TrueType font, FoxPrint.Font Compatibility Between Windows 3.0 and 3.1Windows 3.0 is not aware of TrueType font technology, and therefore cannot use TrueType fonts.Windows 3.1, however, is aware of Windows 3.0 font formats, and uses font mapping to choose the 3.1 font that most closely resembles an unavailable 3.0 font. NOTE: The Windows 3.1 fonts MS Serif and MS Sans Serif replace the Windows 3.0 fonts Tms Rmn and Helv, respectively. Fixedsys, System, and Terminal FontsThe Fixedsys, System, and Terminal fonts have specific uses in Windows itself, and are not normally used by Windows-based applications such as FoxPro.REFERENCES"Microsoft Windows Resource Kit," version 3.0, page 82 "Microsoft Windows Resource Kit," version 3.1, pages 314 and 317 Additional query words: FoxWin 2.50 greek illegible
|
|
Last Reviewed: August 8, 1999 © 1999 Microsoft Corporation. All rights reserved. Terms of Use. |