Bug 624016 - [translation] "Gtk-WARNING **: Whoever translated default:LTR did so wrongly." for LANG=my_MM
Summary: [translation] "Gtk-WARNING **: Whoever translated default:LTR did so wrongly....
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: rhn-client-tools   
(Show other bugs)
Version: 6.0
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Milan Zázrivec
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-13 12:41 UTC by Jan Hutař
Modified: 2010-11-23 14:54 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-11-23 14:54:56 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Jan Hutař 2010-08-13 12:41:25 UTC
Description of problem:
When I start rhn_register with LANG=my_MM, I get an Gtk-WARNING.


Version-Release number of selected component (if applicable):
rhn-client-tools-1.0.0-36.el6.noarch


How reproducible:
always


Steps to Reproduce:
1. # LANG=my_MM rhn_register


Actual results:
# LANG=my_MM rhn_register

(rhn_register:25937): Gtk-WARNING **: Whoever translated default:LTR did so wrongly.


Expected results:
No warning as for other languages.

Comment 1 Jan Pazdziora 2010-11-23 14:40:21 UTC
I don't think we support RHEL 6 on LANG my_MM.

Comment 2 Jan Hutař 2010-11-23 14:50:35 UTC
This is why I thought we do (well, ran this on RHEL5/F14 as I do not have RHEL6 handy):

# rpm -ql rhn-client-tools | grep my
/usr/share/locale/my/LC_MESSAGES/rhn-client-tools.mo
# locale --all-locales | grep '^my'
my_MM
my_MM.utf8

Comment 3 RHEL Product and Program Management 2010-11-23 14:54:56 UTC
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.