public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "maiku.fabian at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug localedata/17475] New Bhilodi and Tulu locales
Date: Thu, 05 Mar 2015 08:21:00 -0000 [thread overview]
Message-ID: <bug-17475-131-zRaBcAHiva@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17475-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17475
Mike FABIAN <maiku.fabian at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
CC| |maiku.fabian at gmail dot com
Resolution|FIXED |---
--- Comment #8 from Mike FABIAN <maiku.fabian at gmail dot com> ---
(In reply to Tatiana Udalova from comment #2)
> ISO codes for tcy were taken from here:
> http://en.wikipedia.org/wiki/ISO_639:t
> ISO codes for bhb were taken from here:
> http://en.wikipedia.org/wiki/ISO_639:b
>
> "terminology language code `tcy' not defined" problem also was fixed in our
> patch.
> Current localedef has no information about tulu and bhilodi languages. Such
> information should be added to libc/locale/iso-639.def.
> Our patch adds this information, but localedef should be rebuilded after
> that.
The wikipedia links given seem to show that there are no iso 639-1 codes
for these languages.
So the locales should probably use the 3 letter iso 639-3 codes:
tu_IN -> tcy_IN
bh_IN -> bhb_IN
(The 2 letter code "bh" is already the iso 639-1 code for Bihari:
http://en.wikipedia.org/wiki/Bihari_languages)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2015-03-05 8:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 8:25 [Bug localedata/17475] New: " t.udalova at samsung dot com
2014-10-10 9:53 ` [Bug localedata/17475] " pravin.d.s at gmail dot com
2014-10-10 10:15 ` t.udalova at samsung dot com
2014-10-10 10:43 ` pravin.d.s at gmail dot com
2014-10-13 7:30 ` t.udalova at samsung dot com
2014-11-12 11:48 ` cvs-commit at gcc dot gnu.org
2014-11-12 11:59 ` siddhesh at redhat dot com
2015-03-05 8:21 ` maiku.fabian at gmail dot com [this message]
2015-03-05 11:54 ` pravin.d.s at gmail dot com
2015-06-17 12:27 ` pravin.d.s at gmail dot com
2015-07-15 10:38 ` cvs-commit at gcc dot gnu.org
2015-07-15 10:41 ` siddhesh at redhat dot com
2015-07-17 21:40 ` raj.khem at gmail dot com
2015-07-21 2:11 ` cvs-commit at gcc dot gnu.org
2015-07-21 5:02 ` pravin.d.s at gmail dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-17475-131-zRaBcAHiva@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).