Bug 129997

Summary: wrong localization domain
Product: Red Hat Cluster Suite Reporter: Victor Ashik <victor>
Component: redhat-config-clusterAssignee: Jim Parsons <jparsons>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: low Docs Contact:
Priority: medium    
Version: 3CC: cluster-maint
Target Milestone: ---Keywords: EasyFix, i18n, StringChange
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-12-20 22:40:13 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Victor Ashik 2004-08-16 10:44:23 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030922

Description of problem:
We do not see localized messages in GUI of redhat-config-cluster when
LANG=ru_RU.UTF-8. strace shows that utility is looking for
config-cluster.mo instead of redhat-config-cluster.mo

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install redhat-config-cluster
2. take updated ru.po from CVS
3. msgfmt ru.po -o
4. LANG=ru_RU.UTF-8 redhat-config-cluster


Actual Results:  Partially localized GUI

Expected Results:  Completely localized GUI

Additional info:

The guilty is:

gettext.bindtextdomain(PROGNAME, "/usr/share/locale")

which does bind to cluster-config instead of redhat-config-cluster as
expected by rpm packager
Comment 1 Jim Parsons 2004-08-26 17:42:36 EDT
This will definitely be fixed in the next release. This bug has given
me  reason to re-aquaint myself with the 'info gettext' docs. :-)
Comment 2 Jim Parsons 2004-09-21 11:37:38 EDT
This fix has been checked in.
Comment 3 John Flanagan 2004-12-20 22:40:13 EST
An advisory has been issued which should help the problem 
described in this bug report. This report is therefore being 
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, 
please follow the link below. You may reopen this bug report 
if the solution does not work for you.