![]() | ![]() | ![]() |
SAS Web Report Studio provides font selection lists for use with objects such as headers, footers, text objects, graphs, and tables. The selection of fonts provided for use with each object depends on the object and the contents of the following five files.
| File | Editable | Font selection lists | Font installation3 |
|---|---|---|---|
| styles.xml1 | No | All objects2 | Middle tier for the server fonts and client (browser) machine for the client fonts |
| ServerFonts.xml | No | Graphs (except titles) | Middle tier |
| ClientFonts.xml | No | Headers, footers, text objects, tables, and graph titles | Client (browser) machine |
| LocalServerFonts.xml | Yes | Graphs (except titles) | Middle tier |
| LocalClientFonts.xml | Yes | Headers, footers, text objects, tables, and graph titles | Client (browser) machine |
|
1 There are also localized versions of the styles.xml file. The locale is appended to the file name. For example, styles_ja.xml is the file used for the Japanese locale. 2 The styles.xml file includes both client and server fonts. 3 For the UNIX and z/OS environments, fonts must be installed correctly and loaded by the JVM in order for SAS Web Report Studio to render them correctly. Both custom fonts, as well as true type fonts supplied by SAS, should be installed in the jre.../lib/fonts directory. See your UNIX or z/OS documentation for commands that apply to font installations. |
|||
Note: This SAS note does not explain how to configure the display of special fonts in PDF reports. For information on that topic, see SAS Note 49401. p>
You can make the following customizations to the font selection lists in SAS Web Report Studio.
Note: You cannot remove any of the fonts that are provided by the styles.xml file.
To make these changes, you modify the LocalClientFonts.xml and LocalServerFonts.xml files. To create these local font files, navigate to the customer folder in the installation directory for SAS Web Report Studio. A typical location is SAS-configuration-directory \Lev1\Web\Applications\SASWebReportStudio4.x\customer
Depending on which font selection list that you want to customize, perform one or both of these tasks:
Open the new file in a plain text editor, and make changes as explained in the next three sections.
After saving your changes, restart your web application server.
To add a font, you enter a new font element just above the </fonts> tag at the bottom of the local font file. Following is an example of a new font element.
The following table explains the font element attributes.
| Attribute | Description | Notes |
|---|---|---|
| actualfont | The font that is saved in the report XML. In the example, Arial is the font that will be stored with the report. | Typically, the actual font is the same as the display font. The value for this attribute should match the name of the installed font. Otherwise, a font substitution might occur. |
| displayfont | The font name that is displayed in the font selection list. In the example, MS Gothic will appear in the list. | If you add a font element with the same display font value as a font element in the ServerFonts.xml or ClientFonts.xml file, then the attributes of the font element in the local font file take precedence. For example, if the ClientFonts.xml file contains an actual font value of NSimSun for the display font Courier New, but the LocalClientFonts.xml file contains an actual font value of MS Mincho for the display font Courier New, then MS Mincho is saved with the report when Courier New is selected from the applicable font selection list. |
| locale | Identifies the font that should be used when SAS Web Report Studio is running in one or more specified locales. In this example, MS Gothic will appear in the font selection list when SAS Web Report Studio is running in the French Canadian locale ("fr_CN") or the German ("de") locale. | As the value for the locale attribute, you can specify both a language and a country code (for example, "fr_CN"), or you can specify just the language code (for example, "de"), or you can use both forms (for example, "fr_CN,de"). For a list of locales and country codes, see LOCALE= Values |
Each local font file includes in its comments a list of the predefined server or client fonts, depending on which local font file that you are editing. Use this list to determine which name to use in the suppress element. The name of the font is case sensitive.
To suppress a single font, you use the following syntax
To suppress multiple fonts, separate the font names with a comma.
To suppress all of the predefined fonts, you use the following syntax:
The font elements in the ClientFonts.xml file do not include a locale attribute, which means that all of the fonts in the file are used to populate the font selection lists for headers, footers, text, tables, and graph titles for all locales in which SAS Web Report Studio is running.
If you add a font element to the LocalClientFonts.xml file that includes a locale attribute, then only those font elements that also specify that locale attribute are subsequently used to populate the font selection lists. For this reason, you typically do not include the locale attribute when adding fonts to the LocalClientFonts.xml file.
If you do specify a locale attribute, then you must also include font elements for any font in the ClientFonts.xml file that you want to continue to use. For example, say that you want to add MS Gothic with a locale attribute and you also want to keep the predefined fonts Century Gothic and Tahoma. Your addition to the LocalClientFonts.xml file might look like this:
After you restart your web application server, the font selection lists for headers, footers, text, tables, and graph titles will include MS Gothic, Century Gothic, Tahoma, and the fonts from the localized styles.xml files.
Note: The fonts specified by the styles.xml file are always included, regardless of locale.
Some of font elements in the ServerFonts.xml file do include the locale attribute. For example, here are two of the font elements from the ServerFonts.xml file:
So, if you are running in the Japanese ("ja,ja_JP") locale, then MS Mincho is stored with the report when you select Courier New from the font selection list. However, if you are running in the Chinese ("zh,zn_CN") or Chinese Singapore ("zh_SG) locale, then NSimSun is stored with the report when you select Courier New.
When adding a font element to the LocalServerFonts.xml file, be sure to specify the correct locale value for your environment. For example, if you are running in a Japanese locale, then the locale attribute value for your new font should be "ja,ja_JP".
Note: The fonts specified by the styles.xml file are always included, regardless of locale.
For the client fonts, if either the display font or the actual font is not available to the browser (for example, it is not installed or it is not installed in the expected location), then the browser chooses a substitution font. For the server fonts, Java manages the substitution.
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Web Report Studio | Microsoft Windows 2000 Advanced Server | 3.1 | 9.1 TS1M3 SP4 | ||
| Microsoft Windows 2000 Datacenter Server | 3.1 | 9.1 TS1M3 SP4 | ||||
| Microsoft Windows 2000 Server | 3.1 | 9.1 TS1M3 SP4 | ||||
| Microsoft Windows 2000 Professional | 3.1 | 9.1 TS1M3 SP4 | ||||
| Microsoft Windows NT Workstation | 3.1 | 9.1 TS1M3 SP4 | ||||
| Microsoft Windows Server 2003 Datacenter Edition | 3.1 | 9.1 TS1M3 SP4 | ||||
| Microsoft Windows Server 2003 Enterprise Edition | 3.1 | 9.1 TS1M3 SP4 | ||||
| Microsoft Windows Server 2003 Standard Edition | 3.1 | 9.1 TS1M3 SP4 | ||||
| Microsoft Windows XP Professional | 3.1 | 9.1 TS1M3 SP4 | ||||
| Windows Vista | 3.1 | 9.1 TS1M3 SP4 | ||||
| Windows Vista for x64 | 3.1 | 9.1 TS1M3 SP4 | ||||
| 64-bit Enabled AIX | 3.1 | 9.1 TS1M3 SP4 | ||||
| 64-bit Enabled Solaris | 3.1 | 9.1 TS1M3 SP4 | ||||
| HP-UX IPF | 3.1 | 9.1 TS1M3 SP4 | ||||
| Type: | Usage Note |
| Priority: |
| Date Modified: | 2012-11-15 13:39:52 |
| Date Created: | 2012-11-08 13:49:11 |


