Troubleshooting Web Output |
If your presentation displays an incorrect text font on a given client computer, then the cause may be that the client computer maps a logical font name such as Courier to a different physical font set. If the logical font is not mapped to any physical font, Java uses a default font.
When you are using the Java and ActiveX devices or the DS2TREE or DS2CONST macros, the actual fonts used are determined at run time. The fonts are resolved based on the fonts available on the system where the graph is viewed. When you use the JAVA or ACTIVEX device, the fonts specified by the styles are also specified in the HTML or RTF file that is generated. When the file is viewed, if a font is not available, the font mapper on the system where the file is viewed determines the font that is substituted.
It is recommended that you specify system fonts whenever possible. See Determining What Fonts Are Available and TrueType Fonts That Are Supplied by SAS for more information.
For programs that use the JAVAMETA device, specify one of these font names: Helvetica, TimesRoman, Courier, Dialog, DialogInput, or ZapfDingbats; or, specify one of these font styles: serif, sansserif, or monospaced. You can also specify the bold, italic, or italic bold versions of any of these fonts except ZapfDingbats. For example, HelveticaBold, sansserifItalic, or DialogInputItalicBold. If you specify a font style instead of a specific font, the actual font used is determined at run time based on the fonts available on the system where the output is viewed.
Copyright © 2010 by SAS Institute Inc., Cary, NC, USA. All rights reserved.