Bug 230104 - Not all expressions for openoffice.org2 are correctly displayed in encoding ta_IN.utf8
Not all expressions for openoffice.org2 are correctly displayed in encoding t...
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: openoffice.org (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Caolan McNamara
Depends On:
  Show dependency treegraph
Reported: 2007-02-26 12:47 EST by Jan Lieskovsky
Modified: 2007-11-16 20:14 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-02-26 14:21:14 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jan Lieskovsky 2007-02-26 12:47:46 EST
Description of problem:
After setting the locale to "ta_IN.utf8" openoffice.org2 suite binaries:
oowriter2, oocalc2 ... displays some menubars in English and some in
this exotic encoding. 

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

How reproducible:

Steps to Reproduce:
1. Set the encoding to "ta_IN.utf8" (export LANG=ta_IN.utf8)
2. Run some binary from the openoffice.org2 suite: oowriter2, oocalc2 for
3. You will see that some button text and menubars will be displayed in 
   English and some in this exotic encoding.
Actual results:
Menubars and button text is mixed.

Expected results:
All button text should be displayed in one language.

Additional info:
This bug is related with testing advisory RHEA-2007:9031.
Comment 1 Caolan McNamara 2007-02-26 14:12:58 EST
I have no control over the coverage of translations. I'd be interested in a
comparison against the OOo shipped in RHEL-5 which should be about the same as
this one. But either way I simply have no additional translations.
Comment 2 RHEL Product and Program Management 2007-02-26 14:21:14 EST
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request. 

Note You need to log in before you can comment on or make changes to this bug.