From: "j.faithw at yahoo dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/19066] New: ar_SA abbreviated day and month names are in English
Date: Mon, 05 Oct 2015 13:25:00 -0000 [thread overview]
Message-ID: <bug-19066-716@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=19066
Bug ID: 19066
Summary: ar_SA abbreviated day and month names are in English
Product: glibc
Version: 2.24
Status: NEW
Severity: normal
Priority: P2
Component: localedata
Assignee: unassigned at sourceware dot org
Reporter: j.faithw at yahoo dot com
CC: libc-locales at sourceware dot org
Target Milestone: ---
The localedata/locales/ar_SA file has English data for abday and abmon.
I don't know for certain that this is wrong but it probably is.
For reference when I run:-
for i in `locale -a|grep '^ar_.*\.utf8'`; do
LC_ALL="$i" date "+$i: day ab:%a full:%A month ab:%b full:%B";
done
I get the following output:-
ar_AE.utf8: day ab:ن full:الاثنين month ab:أكت full:أكتوبر
ar_BH.utf8: day ab:ن full:الاثنين month ab:أكت full:أكتوبر
ar_DZ.utf8: day ab:ن full:الاثنين month ab:أكت full:أكتوبر
ar_EG.utf8: day ab:ن full:الاثنين month ab:أكت full:أكتوبر
ar_IN.utf8: day ab:ن full:الاثنين month ab:أكت full:أكتوبر
ar_IQ.utf8: day ab:ن full:الاثنين month ab:أكت full:أكتوبر
ar_JO.utf8: day ab:الاثنين full:الاثنين month ab:تشرين الأول full:تشرين الأول
ar_KW.utf8: day ab:ن full:الاثنين month ab:أكت full:أكتوبر
ar_LB.utf8: day ab:الاثنين full:الاثنين month ab:تشرين الأول full:تشرين الأول
ar_LY.utf8: day ab:ن full:الاثنين month ab:أكت full:أكتوبر
ar_MA.utf8: day ab:ن full:الاثنين month ab:أكت full:أكتوبر
ar_OM.utf8: day ab:ن full:الاثنين month ab:أكت full:أكتوبر
ar_QA.utf8: day ab:ن full:الاثنين month ab:أكت full:أكتوبر
ar_SA.utf8: day ab:Mon full:الإثنين month ab:Oct full:تشرين الأول
ar_SD.utf8: day ab:ن full:الاثنين month ab:أكت full:أكتوبر
ar_SY.utf8: day ab:الاثنين full:الاثنين month ab:تشرين الأول full:تشرين الأول
ar_TN.utf8: day ab:ن full:الاثنين month ab:أكت full:أكتوبر
ar_YE.utf8: day ab:ن full:الاثنين month ab:أكت full:أكتوبر
Clearly ar_SA has Mon and Oct which stand out.
I have checked git and English has been used since the earliest version from
2000-02-12.
As I understand it the raw data that most of the locale files were based on
came from the CLDR many years ago. Looking at the current CLDR(release 28
http://unicode.org/Public/cldr/28/core.zip) the ar_SA.xml file has no variation
from the base ar.xml file.
There is a locale explorer available here
http://demo.icu-project.org/icu-bin/locexp
the Saudi Arabia link is
http://demo.icu-project.org/icu-bin/locexp?d_=en&_=ar_SA
But note that http://www.unicode.org/cldr/charts/28/
warns that the source xml data is more up to date than anything else and may
contain more information.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2015-10-05 13:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 13:25 j.faithw at yahoo dot com [this message]
2017-07-03 8:04 ` [Bug localedata/19066] " maiku.fabian at gmail dot com
2017-07-06 14:23 ` cvs-commit at gcc dot gnu.org
2017-07-11 10:56 ` maiku.fabian at gmail dot com
2017-07-11 10:56 ` cvs-commit at gcc dot gnu.org
2017-07-11 10:58 ` 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-19066-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).