Global Deployment Guide > Configuring Global Deployments >

Configuring Cascading Style Sheets to Specify Different Fonts

To successfully run Siebel Business Applications, your cascading style sheet files (CSS files) for Siebel applications must specify fonts that are available on your systems and that support the languages and locales in which you will run the applications.

By default, the style sheets specify fonts for Windows platforms only. The specified fonts are not Unicode fonts, and may not support the character sets you require for all languages you may deploy. (The term Unicode fonts is used here loosely to refer to any font that contains a wide range of the characters required to support the many languages included in the Unicode standard.)

You can use utilities on your client systems, such as the Character Map utility on Windows, to determine which characters are available in any installed font.

For some example font settings that may be suitable on different operating system platforms for supported languages or locales, see Table 8.

Some scenarios in which you may need to modify font specifications in your cascading style sheets include the following:

• If your database uses Unicode, and some users need to be able to view data using multiple languages, then the cascading style sheets applicable to these users may need to be modified to specify Unicode fonts.

  For example, if U.S. English (ENU) users need to view data using Japanese (JPN) characters, then Unicode fonts would be required for the ENU users, such as to change from Arial to Arial Unicode MS. If the JPN users do not require viewing data in other languages, then a Shift-JIS font may be specified for these users, because the display characteristics may be more suitable.

  NOTE:  Style sheet files can include font names that contain non-ASCII characters only if the file is saved using UTF-8 encoding.

• If you are deploying your Siebel applications with any language that is not supported by the default fonts specified in the cascading style sheets, then the style sheets applicable to users for this language must be modified to specify a suitable font. See example fonts listed in Table 8.
• If you are deploying Siebel applications on client machines running UNIX (using standard interactivity), your style sheets must specify fonts that are available on your UNIX systems. See example fonts listed in Table 8.
• You may also need to specify different fonts in order to display special symbols such as mathematical symbols, to change the font to suit your company's design standards, and so on. (These scenarios are not specifically related to deploying languages.)

You may need to modify multiple cascading style sheet files, depending on which Siebel products and features you are deploying. Cascading style sheet files include main.css (for employee applications, which use high interactivity), dCCmain.css (for customer applications, which use standard interactivity), jctrls.css (also high interactivity), and several others.

NOTE:  For Siebel applications that use high interactivity mode, the first font specified in each applicable cascading style sheet must be valid. Additional font names specified in a list are not used.

Cascading style sheet files and other types of files, such as image files, are copied from the Siebel Server to the Web server each time the Web server is restarted. Alternatively, administrators can update these files explicitly, as described in the Siebel Installation Guide for the operating system you are using.

For more information about modifying cascading style sheets, see Configuring Siebel Business Applications and the Siebel Developer's Reference. For more information about deploying cascading style sheet files, see Going Live with Siebel Business Applications. See also FAQ 2104 on Siebel SupportWeb.

Table 8 lists some example font settings that may be suitable on different operating system platforms for supported languages or locales. For multilingual Unicode deployments, it may be suitable to specify Arial Unicode MS in place of Arial, in order to be able to display data in different languages.