Bug 497971 - [ne_NP] libX11 does not support locale ne_NP.UTF-8
Summary: [ne_NP] libX11 does not support locale ne_NP.UTF-8
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: libX11
Version: 11
Hardware: All
OS: Linux
high
medium
Target Milestone: ---
Assignee: Søren Sandmann Pedersen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 502433
Blocks: 497038
TreeView+ depends on / blocked
 
Reported: 2009-04-28 07:00 UTC by Peng Huang
Modified: 2014-06-18 09:11 UTC (History)
9 users (show)

Fixed In Version: 1.2.1-2.fc11
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-06-16 01:39:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Test code for this problem. (152 bytes, text/plain)
2009-04-28 07:00 UTC, Peng Huang
no flags Details


Links
System ID Private Priority Status Summary Last Updated
FreeDesktop.org 21560 0 None None None Never

Description Peng Huang 2009-04-28 07:00:37 UTC
Created attachment 341528 [details]
Test code for this problem.

Description of problem:
libX11 does not support locale ne_NP.UTF-8

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


How reproducible:
XSupportsLocale does not return the true if $LANG  is ne_NP.UTF-8

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 A S Alam 2009-04-28 07:41:16 UTC
Is version of libX11 is
libX11-1.2-3.fc11

Comment 2 Peng Huang 2009-05-05 05:26:57 UTC
Yeah.
libX11-1.2-3.fc11.i586

Comment 3 Jens Petersen 2009-05-05 05:31:09 UTC
Could you attach a patch and also check/file this issue upstream please at
freedesktop?

Comment 4 Peng Huang 2009-05-06 03:29:44 UTC
The upstream bug is http://bugs.freedesktop.org/show_bug.cgi?id=21560

Comment 5 Parag Nemade 2009-05-07 06:07:29 UTC
Here is test scratch build to check if one can input in ne_NP
http://koji.fedoraproject.org/koji/taskinfo?taskID=1340100

Comment 6 Parag Nemade 2009-05-25 08:32:13 UTC
To libX11 maintainers,
Can it be possible to build new libX11 with patch accepted upstream?
Thanks.

Comment 7 Fedora Update System 2009-05-26 07:09:45 UTC
libX11-1.2.1-2.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/libX11-1.2.1-2.fc11

Comment 8 Fedora Update System 2009-05-27 19:08:03 UTC
libX11-1.2.1-2.fc11 has been pushed to the Fedora 11 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update libX11'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-5523

Comment 9 Bug Zapper 2009-06-09 14:41:40 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 10 Ilpo Nyyssonen 2009-06-15 16:18:31 UTC
Is it intentional that several files under /usr/share/X11/locale are empty?

# rpm -qf locale.dir 
libX11-1.2.1-2.fc11.i586
# find -size 0
./C/Compose
./el_GR.UTF-8/XI18N_OBJS
./el_GR.UTF-8/XLC_LOCALE
./iscii-dev/Compose
./isiri-3342/Compose
./iso8859-11/Compose
./ja.S90/Compose
./ja.U90/Compose
./ja_JP.UTF-8/Compose
./ko_KR.UTF-8/Compose
./microsoft-cp1251/Compose
./microsoft-cp1255/Compose
./microsoft-cp1256/Compose
./nokhchi-1/Compose
./tatar-cyr/Compose
./th_TH/Compose
./th_TH.UTF-8/Compose
./tscii-0/Compose
./zh_CN.UTF-8/Compose
./zh_HK.UTF-8/Compose
./zh_TW.UTF-8/Compose
./am_ET.UTF-8/XI18N_OBJS
./am_ET.UTF-8/XLC_LOCALE
./fi_FI.UTF-8/XI18N_OBJS
./fi_FI.UTF-8/XLC_LOCALE

And why fi_FI.UTF-8 is not supported?

$ LC_ALL=fi_FI.UTF-8 xterm
Warning: locale not supported by Xlib, locale set to C

Comment 11 Fedora Update System 2009-06-16 01:38:52 UTC
libX11-1.2.1-2.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 12 Parag Nemade 2009-06-16 04:30:04 UTC
(In reply to comment #10)
> Is it intentional that several files under /usr/share/X11/locale are empty?

> # rpm -qf locale.dir 
> libX11-1.2.1-2.fc11.i586
> # find -size 0
> ./C/Compose
> ./el_GR.UTF-8/XI18N_OBJS
> ./el_GR.UTF-8/XLC_LOCALE
> ./iscii-dev/Compose
> ./isiri-3342/Compose
> ./iso8859-11/Compose
> ./ja.S90/Compose
> ./ja.U90/Compose
> ./ja_JP.UTF-8/Compose
> ./ko_KR.UTF-8/Compose
> ./microsoft-cp1251/Compose
> ./microsoft-cp1255/Compose
> ./microsoft-cp1256/Compose
> ./nokhchi-1/Compose
> ./tatar-cyr/Compose
> ./th_TH/Compose
> ./th_TH.UTF-8/Compose
> ./tscii-0/Compose
> ./zh_CN.UTF-8/Compose
> ./zh_HK.UTF-8/Compose
> ./zh_TW.UTF-8/Compose
> ./am_ET.UTF-8/XI18N_OBJS
> ./am_ET.UTF-8/XLC_LOCALE
> ./fi_FI.UTF-8/XI18N_OBJS
> ./fi_FI.UTF-8/XLC_LOCALE

On my rawhide (F12) I got output as
./ja.S90/Compose
./microsoft-cp1251/Compose
./isiri-3342/Compose
./tatar-cyr/Compose
./ja.U90/Compose
./iso8859-11/Compose
./tscii-0/Compose
./microsoft-cp1255/Compose
./iscii-dev/Compose
./C/Compose
./am_ET.UTF-8/XI18N_OBJS
./am_ET.UTF-8/XLC_LOCALE
./th_TH.UTF-8/Compose
./zh_CN.UTF-8/Compose
./el_GR.UTF-8/XI18N_OBJS
./el_GR.UTF-8/XLC_LOCALE
./ja_JP.UTF-8/Compose
./nokhchi-1/Compose
./zh_HK.UTF-8/Compose
./zh_TW.UTF-8/Compose
./ko_KR.UTF-8/Compose
./th_TH/Compose
./microsoft-cp1256/Compose

My guess is that those encodings have no characters to represent them. like See zh_HK is using Big5 so you will find information in zh_HK.big5/Compose
Same for ko_KR.UTF-8. Look into ko/Compose. And for zh_CN.UTF-8 look for actual encoding zh_CN.gb18030



> 
> And why fi_FI.UTF-8 is not supported?
it is supported on F-11 also.

> 
> $ LC_ALL=fi_FI.UTF-8 xterm
> Warning: locale not supported by Xlib, locale set to C  

Yes. I got same output. I quickly tested fi_FI locale on my English F-12 desktop as
LANG=fi_FI.UTF-8 gedit
it worked.

I also see no xterm.mo is present for any locale. So looks like we have no translations for xterm. But I see many applications translations for fi_FI.


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