Patch-ID# 118044-14

NOTE:
***********************************************************************
READ THE TERMS OF THE AGREEMENT ("AGREEMENT") IN THE LEGAL_LICENSE.TXT
FILE CAREFULLY BEFORE USING THIS SOFTWARE. BY USING THE SOFTWARE, YOU
AGREE TO THE TERMS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE
TERMS, PROMPTLY DESTROY THE UNUSED SOFTWARE.
***********************************************************************

Keywords: java_es linux rhel3.0 uwc l10n
Synopsis: RHEL3:
Date: Oct/14/2005


Install Requirements: Additional instructions may be listed below                      
                      
Solaris Release: 
Note: Redhat


SunOS Release: 
Note: RHEL3.0


Unbundled Product: Sun Java System Communications Express

Unbundled Release: 6.1

Xref: 

Topic: Sun Java System Communications Express 6.1 RHEL 3.0: L10N patch

Relevant Architectures: i386

BugId's fixed with this patch: 5039992 6177575 6177586 6177601 6179257 6179335 6179454 6181484 6182599 6182987 6183001 6183075 6183141 6184259 6184282 6190097 6191350 6194188 6197782 6197821 6198511 6200986 6201004 6204672 6207225 6210903 6213979 6239959 6281367 6281378 6282077 6306399

Changes incorporated in this version: 6190097 6191350 6198511 5039992 6177586 6181484 6200986 6177575 6177601 6179257 6179335 6179454 6182599 6182987 6183001 6183075 6183141 6184259 6184282 6194188 6197782 6197821 6201004 6204672 6207225 6210903 6213979 6239959 6281367 6281378 6282077 6306399

Patches accumulated and obsoleted by this patch: 

Patches which conflict with this patch: 

Patches required with this patch: 

Obsoleted by: 

Files included with this patch: 


Note: sun-uwc-de-6.1-11.9.i386.rpm
sun-uwc-es-6.1-11.9.i386.rpm
sun-uwc-fr-6.1-11.9.i386.rpm
sun-uwc-ja-6.1-11.9.i386.rpm
sun-uwc-ko-6.1-11.9.i386.rpm
sun-uwc-zh_CN-6.1-11.9.i386.rpm
sun-uwc-zh_TW-6.1-11.9.i386.rpm

Problem Description:

6190097 JES3_b07: missing l10n rpm packages of AM and UWC or rpm name mismatch
6191350 JES3 Linux B7: UWC l10n files installed into wrong location
6198511 JES3_b08: 1122 nightly: l10n_ja: Some GUIs are still in English
5039992 "Match ... of the following conditions:" translation is not good
6177586 JES3:10/11_nightly: "Home" is wrongly translated in zh_TW/zh_CN
6181484 JES3:build06a:l10n_ko:wrong translation on New Event and New task making page.
6200986 JES3_b08: Many overtranslated date patterns in Spanish i18n.properties
6177575 JES3_B07 + 11/2_l10n_nightly: Mail folder names are not translated
6177601 JES3:10/11_nightly: Wrong translation for the week days in zh_TW/zh_CN
6179257 JES3:b06a:zh_TW: "Trash" Folder name translation should be consistant
6179335 JES3:b06a:l10n: Some characters displayed garbled in folder creation gui
6179454 JES3:b06a:l10n: "(O)" should be remove from the end of "Format" translation
6182599 JES3_b06a: l10n_fr: some string are pseudolocalized
6182987 JES3:build06a:l10n_ko:wrong translation for "Sent" on current folder drop down list on Mail tab.
6183001 JES3:build06a:l10n_ko: English word "in" shows on Address Book search.
6183075 JES3:b06a:l10n_zh_cn: wrong translation for "Title" in "New Event" and "New Task" window.
6183141 JES3_b06a: l10n_fr: overtranslated date pattern in i18n.properties
6184259 Some translations for "New Task"/"New Event" gui need be revised for zh_TW
6184282 JES3:b06a:i18n: "Reminder" in Reminder email should be translated
6194188 JES3:b07 "Maximum size" translation need be revised in zh_TW and zh_CN
6197782 JES3_b8: l10n_ja: Not integrated final mail OLH
6197821 JES3_b08: l10n ja: wrong image file directory in mail OLH
6201004 JES3_b08: l10n_es: Crippled Calendar tab name in Mail view
6204672 JES_08: l10n_ko: wrong translation for "First" and "Last" name under Options
6207225 JES3:b08 The title of address book translation in "Printable" need be revised for zh_CN and zh_TW
6210903 JES3:build 9:korean compose window shows english messages
6213979 jes3:b09 Some nessages need translation for zh_TW uwc command line configuration
6239959 SJES3: l10n: Wrong Japanese translation for 'Server Target Name' in some messages
6281367 jes4_b5:l10n:Incorrect translation "Home" in UI on zh_CN,zn_TW locale.
6281378 JES4_b5:zh_CN Inconsistent translation for "Logout" in UWC UI.
6282077 JES4:b05a: Translations for uwc claendar event types need be revised in zh-CN/zh-TW
6306399 Unable to use Mail Filter functionalities in de locale

Patch Installation Instructions:
--------------------------------
To install this patch, run the command
   rpm -F <rpmname>
This will freshen your existing RPM installation.
Note that if this is a relocatable binary RPM and you have installed
into a non-default location using the --prefix switch, you must
specify the --prefix switch with the non-default location when you
install this patch.
 
Consult the rpm(1) man page for more details.

Special Install Instructions:
-----------------------------
 ----------------------------------------------------------------------
  IMPORTANT NOTE:
    These instructions are applicable if you have configured 
    Communications Express prior to the installation of this patch RPM.
 
    If you intend to configure Communications Express after installation
    of this patch RPM, you do not need to perform any patch configuration 
    procedures and you can ignore all instructions provided below. 
  ----------------------------------------------------------------------
 
After you finish the patch RPM installation process (using the "rpm -F <rpm>") ,
please perform these steps in order to apply the patch files to the 
Communications Express deployment. Perform the steps as mentioned in
the order below:
 
  a) Run <uwc-basedir>/sbin/patch-config 
  b) Run <uwc-basedir>/sbin/install-newconfig
  c) Restart the Web Container Instance on which the Communications Express
     application is deployed for the changes to take effect.
 
  Where, <uwc-basedir> represents the package base directory
  of Communication Express. example: /opt/sun/uwc
 
How to run the config tools "patch-config" and "install-newconfig":-
 
  The below scenario is explained by taking some example directories.
  * Let us Consider that the Communication Express package is installed
    in "/opt/sun/uwc" directory. The tools are available at:
        /opt/sun/uwc/sbin/patch-config and /opt/sun/uwc/sbin/install-newconfig
  * The Communication Express application is deployed
    in "/var/opt/sun/uwc" directory.
  * The Communication Express patch 118044-14 needs to be configured
  * The patch-config tool shall be invoked as:
        /opt/sun/uwc/sbin/patch-config -d /var/opt/sun/uwc /opt/sun/uwc/install/patch/118044-14
  * The install-newconfig tool shall be invoked as:
        /opt/sun/uwc/sbin/install-newconfig /opt/sun/uwc/install/patch/118044-14
 
How the patch config process works:-
 
  To apply the patch files and patch configuration to Communications Express 
  deployment, the patch-config tool and the install-newconfig tool should be run. 
    a) Run the "patch-config" tool: 
         - This tool prepares the patch files and configuration and gets 
           these files ready to be installed.
         - The new patch file versions are created under
 
             <uwc-basedir>/install/patch/118044-14/save
 
           118044-14 represents the number of the patch that is configured.
           The save directory has the same directory structure layout 
           as the <uwc-basedir> directory, except that the files under
           <uwc-basedir>/lib/config-templates directory are relocated
           to <uwc-basedir>.
         - For each file included in this patch, this tool prepares two files
           under <uwc-basedir>/install/patch/118044-14/save.
 
           The two files are, <file> and <file>.new
           Where,
             <file> represents the file backed up from previous 
                               Communications Express deployment.
             <file>.new represents the new patch file version supplied
                               in this patch. This file will be deployed
                               in the Communications Express deployment 
                               when you run install-newconfig program.
   -----------------------------------------------------------------------
   IMPORTANT NOTE: Please review the changes in the new patch files before 
                   applying them by running install-newconfig program. 
                   To review the changes, please see the difference 
                   between the files <file> and <file>.new
   -----------------------------------------------------------------------
    b) Run the "install-newconfig" tool:
 
         - This tool installs the new patch files prepared by patch-config tool.
         - This program installs all the ".new" files prepared by patch-config
           tool into Communications Express deployment.
 
Patch configuration backout instructions:-
    * To backout the patch configuration from Communications Express deployment,
      please perform the following steps:
 
        i)  Run <uwc-basedir>/sbin/backout-newconfig
 
            For example, to backout the patch 118044-14 configuration from
            Communications Express deployment, run
 
              <uwc-basedir>/sbin/backout-newconfig <uwc-basedir>/install/patch/118044-14
 
              - This tool reverts back the Communications Express deployment
                to the state where it was before the patch configuration
                was applied.
              - This tool also helps maintain a backup of any file modifications
                performed after the last patch configuration under the directory
                "<uwc-basedir>/install/patch/118044-14/save" with 
                an extension ".backup".
 
     -----------------------------------------------------------------------
     IMPORTANT NOTE: Do not run backout-newconfig tool more than once.
                     If you run the tool again, your .backup files may be 
                     overwritten by old data.
     -----------------------------------------------------------------------
 
      ii) Restart the web container instance on which the Communications Express
          application is deployed for the changes to take effect.

README -- Last modified date:  Friday, October 14, 2005

