Enabling applications and pages to support multiple languages

To enable UA applications and pages to support multiple languages simultaneously, use UTF-8 encoding. UTF-8 allows users to place applications from different languages on the same page and also allows application names in different languages.

UA applications are preconfigured with ISO encoding, which typically supports only one or more closely-related language sets.

To enable the portal for UTF-8 support:

1. Open global.properties.xml in WordPad on Windows. This file is located in %JAGUAR%\Repository\WebApplication\onepage\config if you are using EAServer as your application server and UnwiredAccelerator70\tomcat\webapps\onepage\config if you are using Tomcat.

2. Search for the “use_utf8” property and set the value to “true”, which sets the portal to use UTF-8 globally. For example, change this:

   <Property name="use_utf8" value="false" description="(true/false). true to enable global to set the Portal to use UTF-8" menugroup="-1"/>
   

   to this:

   <Property name="use_utf8" value="true" description="(true/false). true to enable global to set the Portal to use UTF-8" menugroup="-1"/>
   

3. Save global.properties.xml and close the text editor.

4. Set the charset property and emailCharset property to UTF-8 for each co-brand you have listed in cobrands.xml.

   The cobrands.xml file contains a definition for each co-brand (portal). See the Unwired Accelerator Administration Guide for more information about co-brands.

   1. Open cobrands.xml in MS WordPad on Windows and in any text editor on UNIX.

      The default cobrands.xml is located in %JAGUAR%\Repository\WebApplication\onepage\config if you are using EAServer as your application server and UnwiredAccelerator70\tomcat\webapps\onepage\config if you are using Tomcat.

   2. Set the charset property to “UTF-8”.

   3. In cobrands.xml, set the e-mailCharset property to “ISO-xxxx-x”.

      E-mail clients typically cannot interpret UTF-8 encoded e-mail messages. However, if your e-mail client can interpret UTF-8 encoded e-mail messages, you can set this value to UTF-8 also.

      For example, change this:

      <CobrandDef rid='1' name='Sybase'
         dir='/fw/cobrands/onepage-1'
         charset='ISO-8859-1'
         emailCharset='ISO-8859-1'
         emailerSetting='1' >
      </CobrandDef>
      

      to this:

      <CobrandDef rid='1' name='Sybase'
         dir='/fw/cobrands/onepage-1'
         charset='UTF-8'
         emailCharset='ISO-8859-1'
         emailerSetting='1' >
      </CobrandDef>
      

5. Set the correct character set in styles.xml for each co-brand you have created. The default styles.xml is located in %JAGUAR%\Repository\WebApplication\onepage\fw\baseapps if you are using EAServer and UnwiredAccelerator70\tomcat\webapps\onepage\fw\baseApps if you are using Tomcat.

   If you have more than one co-brand, you must change the character set in the styles.xml file for each one. The styles.xml for each co-brand is stored within that portal’s co-brands subdirectory; for example, UnwiredAccelerator70\tomcat\webapps\onepage\fw\cobrands\japanese-11.

   An example of this step is to change this:

   <Styles
      charset="charset=iso-8859-1"
      charset_ie="charset=ISO-8859-1"
      charset_nn="charset=ISO-8859-1"
      customerCareEmail="customercare@Sybase.com"
      documentDomain="sybase.com	"/>
   

   to this:

   <Styles
      charset="charset=UTF-8"
      charset_ie="charset=UTF-8"
      charset_nn="charset=UTF-8"
      customerCareEmail="customercare@Sybase.com"
      documentDomain="sybase.com	"/>
   

Copyright © 2005. Sybase Inc. All rights reserved.

View this book as PDF