Custom messages need to be translated if WorkSpace users speak different languages. You might also need to use different colors, font-sizes and images that adapt to the culture of its users. The font-size usually needs to be changed according to the typography selected in the CSS file. It is advisable to define font one or two points larger for Asian characters.
By default, an WorkSpace installation includes an English CSS files and separate CSS files for Japanese, Chinese and Korean. If WorkSpace is used in any of these languages you should redefine the corresponding CSS. If WorkSpace is used in a language different from English and you need to make adjustments to the style of that locale, you should add the CSS file that corresponds to that locale.
If there is no CSS defined for the locale WorkSpace is running in, it uses the CSS defined for English. The CSS defined for English use the suffix -en or use no suffix. For example, although a French CSS file is named customStyle-fr.css, using an -fr suffix, the corresponding English CSS file would be named simply customStyle.css, without an -en suffix.
To localize CSS preferences, follow the procedure described in Localizing Oracle BPM WorkSpace CSS.
To customize the labels and text messages for any of these languages, you define a message bundle for that locale. You can only customize the default supported languages, or a language you add. You must not use this mechanism to add a new language. To localize custom labels and text messages, follow the procedure described in Localizing WorkSpace Labels and Text Messages.
By default, WorkSpace uses a single image set. You can, however, define an image set for a specific locale. If there is no image set defined for the locale WorkSpace is running in, it uses the image set defined for English.
To localize WorkSpace icons, follow the procedure described in Localizing Oracle BPM WorkSpace Icons.
If you want to add a new Language that WorkSpace does not support by default, follow the procedures described in .