From: "cjlhomeaddress at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/19956] New: Is aa_ER@saaho locale really ssy_ER locale?
Date: Fri, 15 Apr 2016 21:27:00 -0000 [thread overview]
Message-ID: <bug-19956-716@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=19956
Bug ID: 19956
Summary: Is aa_ER@saaho locale really ssy_ER locale?
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: localedata
Assignee: unassigned at sourceware dot org
Reporter: cjlhomeaddress at gmail dot com
CC: libc-locales at sourceware dot org
Target Milestone: ---
Given the closeness of Afar and Saho languages, it seems like a formal
possibility that the "Saaho dialect" variant of the aa_ER locale might actually
represent a linguistic entity with a unique iso639 code, specifically ssy.
https://en.wikipedia.org/wiki/Saho_language
We should explore this possibility by going back to the original locale
authors, if possible. If true, we may achieve a result that not only provides
a more accurate language description (ssy), but also removes a non-standard
locale name from glibc. I would imagine an extended period of maintaining a
linked entry before eliminating aa_ER@saaho.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2016-04-15 21:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 21:27 cjlhomeaddress at gmail dot com [this message]
2016-04-15 22:59 ` [Bug localedata/19956] ssy_ER: rename from aa_ER@saaho vapier at gentoo dot org
2016-04-15 22:59 ` [Bug localedata/19956] Is aa_ER@saaho locale really ssy_ER locale? vapier at gentoo dot org
2017-10-21 8:25 ` [Bug localedata/19956] ssy_ER: rename from aa_ER@saaho maiku.fabian at gmail dot com
2017-11-22 8:58 ` maiku.fabian at gmail dot com
2024-01-16 18:34 ` maiku.fabian at gmail dot com
2024-01-18 11:06 ` cvs-commit at gcc dot gnu.org
2024-01-18 11:06 ` cvs-commit at gcc dot gnu.org
2024-01-18 11:07 ` maiku.fabian 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-19956-716@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libc-locales@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).