public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "myllynen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug localedata/16973] New: Fix lang_lib/lang_term as per ISO 639-2
Date: Wed, 21 May 2014 14:00:00 -0000 [thread overview]
Message-ID: <bug-16973-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=16973
Bug ID: 16973
Summary: Fix lang_lib/lang_term as per ISO 639-2
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: localedata
Assignee: unassigned at sourceware dot org
Reporter: myllynen at redhat dot com
CC: libc-locales at sourceware dot org
Created attachment 7610
--> https://sourceware.org/bugzilla/attachment.cgi?id=7610&action=edit
Fix lang_lib/lang_term as per ISO 639-2
lang_lib (which reflects ISO 639-2/B (bibliographic) codes) and lang_term
(which reflects ISO 639-2/T (terminology) codes) should be identical except for
those languages for which ISO 639-2 specifies separate
bibliographic/terminology values.
The attached patch got "silent approval" (i.e., negative responses) on
libc-locales, please see the thread for details:
https://sourceware.org/ml/libc-locales/2014-q2/msg00007.html
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2014-05-21 14:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 14:00 myllynen at redhat dot com [this message]
2014-05-21 14:15 ` [Bug localedata/16973] " myllynen at redhat dot com
2014-05-26 12:01 ` carlos at redhat dot com
2014-06-12 19:17 ` fweimer at redhat dot com
2014-07-01 9:28 ` myllynen at redhat dot com
2014-07-01 9:30 ` myllynen at redhat dot com
2014-07-01 9:31 ` myllynen at redhat dot com
2015-08-11 7:55 ` myllynen at redhat dot com
2015-08-18 14:21 ` cvs-commit at gcc dot gnu.org
2015-08-18 14:21 ` vapier at gentoo dot org
2015-10-29 16:29 ` jsm28 at gcc dot gnu.org
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-16973-131@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).