From: "digitalfreak at lingonborough dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/24296] Orthographic mistakes in 'day' and 'abday' sections in tt_RU (Tatar) locale
Date: Fri, 15 Mar 2019 09:39:00 -0000 [thread overview]
Message-ID: <bug-24296-716-MpaouIf7Ce@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24296-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24296
Rafal Luzynski <digitalfreak at lingonborough dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |digitalfreak@lingonborough.
| |com
--- Comment #1 from Rafal Luzynski <digitalfreak at lingonborough dot com> ---
Thank you mansur for the report. Your patch cannot be easily applied because
it is not formatted by "git format-patch", as a consequence it does not have
the commit comment and your name and email address as an author. Of course you
may decide to disclaim your authorship and remain anonymous or I may copy your
address and name from this bugzilla report (I guess that "mansur" is a nick,
not a full name).
Of course, CLDR is an authoritative source for us so your request is justified.
I can see some more differences between CLDR and glibc content and I would like
to ask if you want updates.
1. All weekday names (full and abbreviated) start with an uppercase letter in
glibc while with lowercase in CLDR. Do you think it should be changed?
2. Abbreviated Wednesday (Wed) in CLDR is spelled "чәр", in glibc "Чәрш",
should it be changed?
3. I ignore the trailing dots in CLDR.
4. This may be a separate issue but I think that all month names in tt_RU are
incorrect in glibc. Can you please review?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-03-15 9:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-03 10:37 [Bug localedata/24296] New: " 6688000 at gmail dot com
2019-03-03 10:38 ` [Bug localedata/24296] " 6688000 at gmail dot com
2019-03-15 9:39 ` digitalfreak at lingonborough dot com [this message]
2019-03-15 17:24 ` 6688000 at gmail dot com
2019-03-15 20:36 ` digitalfreak at lingonborough dot com
2019-03-15 21:28 ` 6688000 at gmail dot com
2019-03-15 22:11 ` digitalfreak at lingonborough dot com
2019-03-16 8:24 ` 6688000 at gmail dot com
2019-03-16 19:11 ` digitalfreak at lingonborough dot com
2019-03-16 21:00 ` cjlhomeaddress at gmail dot com
2019-03-17 10:03 ` 6688000 at gmail dot com
2019-03-19 22:09 ` digitalfreak at lingonborough dot com
2019-03-20 8:32 ` 6688000 at gmail dot com
2019-03-20 21:05 ` cvs-commit at gcc dot gnu.org
2019-03-20 21:19 ` digitalfreak at lingonborough 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-24296-716-MpaouIf7Ce@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).