- To: libc-gnats at gnu dot org, gnats-admin at gnu dot org
- Subject: libc/1962: Tigrigna, Tigre, Ge'ez and Sidamo Needed in glibc-2.2/locale/iso-639.def
- From: Daniel Yacob <yacob at geez dot org>
- Date: Sun, 17 Dec 2000 23:55:01 -0500
>Number: 1962
>Category: libc
>Synopsis: Additional language definitions required for building locales.
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: libc-gnats
>State: open
>Quarter:
>Keywords:
>Class: doc-bug
>Submitter-Id: unknown
>Arrival-Date: Sun Dec 17 23:55:01 -0500 2000
>Cases:
>Originator: Daniel Yacob
>Release: libc-2.2
>Organization:
Ge'ez Frontier Foundation
>Environment:
Host type: i386-pc-linux-gnu
System: Linux zendro 2.2.14 #5 Sun Apr 16 16:34:04 EDT 2000 i686 unknown
Architecture: i686
Addons: crypt linuxthreads nss-v1
Build CC: gcc
Compiler version: 2.95.2 20000313 (Debian GNU/Linux)
Kernel headers: UTS_RELEASE
Symbol versioning: yes
Build static: yes
Build shared: yes
Build pic-default: no
Build profile: yes
Build omitfp: no
Build bounded: no
Build static-nss: no
Stdio: libio
>Description:
I found that localedef broke when it didn't recognize the names of
the language code (tir,ti) for the locale I was compiling. I am
working on a library of locales for 14 languages of Ethiopia and
Eritrea. Many of these languages do not have ISO-639 2 or 3 character
names -in which case what does glibc policy dictate? My present
examples are here:
ftp://ftp.ethiopic.org/pub/locales/
This link is fairly comprehensive for 639 codes:
http://lcweb.loc.gov/standards/iso639-2/englangn.html
>How-To-Repeat:
>Fix:
DEFINE_LANGUAGE_CODE ("Ge'ez", gz, gez, gez)
DEFINE_LANGUAGE_CODE ("Sidamo", sx, sid, sid)
DEFINE_LANGUAGE_CODE ("Tigre", tx, tig, tig)
DEFINE_LANGUAGE_CODE ("Tigrigna", ti, tir, tir)