This is sources Bugzilla
Bugzilla Version 2.17.5
Bugzilla Bug 2799
  Locale/charset combinations missing from localedata/SUPPORTED although mentioned in locale files Last modified: 2006-06-19 23:54:36
     Query page      Enter new bug
Bug#: 2799   Hardware:   Reporter: Leonard den Ottolander <leonard-glibc-bugs@ottolander.nl>
Host: Target: Build:
Product:     Add CC:
Component:   Version:   CC:
Remove selected CCs
Status: RESOLVED   Priority:  
Resolution: WONTFIX   Severity:  
Assigned To: Ulrich Drepper <drepper@redhat.com>   Target Milestone:  
Flags: Requestee:
  backport ()
  examined ()
  testsuite ()
Summary:
Keywords:

Attachment Description Type Created Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 2799 depends on: Show dependency tree
Show dependency graph
Bug 2799 blocks:

Additional Comments:


Leave as RESOLVED WONTFIX
Reopen bug
Mark bug as VERIFIED

View Bug Activity   |   Format For Printing


Description:   Last confirmed: 0000-00-00 00:00 Opened: 2006-06-19 13:45
There are a couple of locale/charset combinations currently unsupported
for which a character set is mentioned in the locale file:

$ grep -i charset az_AZ bg_BG mk_MK POSIX ur_PK wal_ET
az_AZ:% Charset: ISO-8859-9E
bg_BG:% this: bg_BG.CP1251 (CP1251 is for coresponding charset),
bg_BG.KOI8R,
mk_MK:% Charsets: UTF-8, ISO-8859-5, CP1251
POSIX:# Charset: ISO646:1993
ur_PK:% Charset: CP1256
wal_ET:% Charset: UTF-8

Thus the following should be valid additions to localedata/SUPPORTED:

az_AZ.ISO-8859-9/ISO-8859-9 \
bg_BG.KOI8R/KOI8R \
bg_BG.ISO-8859-5/ISO-8859-5 \
mk_MK.CP1251/CP1251 \
ur_PK.CP1256/CP1256 \
wal_ET/UTF-8 \

Note that I've left the defaults as are, so I add
ur_PK.CP1256/CP1256 \
instead of
-ur_PK/UTF-8 \
+ur_PK/CP1256 \
+ur_PK.UTF-8/UTF-8 \

Not sure about these as a POSIX locale is present although undefined in
localedata/SUPPORTED:

POSIX/ISO_646.BASIC \
POSIX.UTF-8/UTF-8 \

I can provide a patch if needed, although the above should be easily cut and
pastable.

------- Additional Comment #1 From Ulrich Drepper 2006-06-19 16:10 -------
I'm not going to add all combinations people might eventually find useful.  This
is why localedef is a program sysadmins can use to customize their systems.

------- Additional Comment #2 From Leonard den Ottolander 2006-06-19 16:23 -------
These are not "combinations that people might eventually find useful". These
character sets are explicitely being mentioned in the locale file as being valid
or even the default.

------- Additional Comment #3 From Leonard den Ottolander 2006-06-19 16:29 -------
This is why I filed bug 2800 separately.

------- Additional Comment #4 From Ulrich Drepper 2006-06-19 23:24 -------
What the locale authors thinks is needed is completely irrelevant.  I only add
the absolute minimum.

There will be no change.  Period.

------- Additional Comment #5 From Leonard den Ottolander 2006-06-19 23:30 -------
Not even the addition of wal_ET/UTF-8? There's no valid locale/charset
combination for wal_ET yet.

------- Additional Comment #6 From Leonard den Ottolander 2006-06-19 23:54 -------
One more thing. localedata/SUPPORTED currently states:

# If you have any additions please file a glibc bug report.

If "only adding the minimum" is your policy you might want to explain that
policy in that file. This might avoid people like me filing bug reports for
issues they perceive as being inconsistent (certain locales supporting charsets
that are not supported in other locales that _explicitely_ mention them). Saves
you and us time. Thanks.

     Query page      Enter new bug
Actions: New | Query | bug # | Reports | Requests   New Account | Log In