From: "6688000 at gmail 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 21:28:00 -0000 [thread overview]
Message-ID: <bug-24296-716-qJZCc3h2st@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24296-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24296
mansur <6688000 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #11660|0 |1
is obsolete| |
--- Comment #4 from mansur <6688000 at gmail dot com> ---
Created attachment 11682
--> https://sourceware.org/bugzilla/attachment.cgi?id=11682&action=edit
Patch file with many new corrections and additions.
Hello, Rafal!
1. In Tatar language weekday names do not begin with upper case unless it is
not a beginning of the sentence. In calendars they usually begin with upper
case, or all letters are used in upper case. In the new patch I used lowercase
just like in the most other glibc locale files.
2. Abbreviated ones depend on the allowed length. For example,
Two letter combinations beginning from Monday: Дш, Сш, Чш, Пҗ, Җм, Шм, Як.
Three letter combinations beginning from Monday: Дүш, Сиш, Чәр, Пән, Җом, Шим,
Якш.
There are also combined 3-4 letter combinations beginning from Monday: Дүш,
Сиш, Чәрш, Пәнҗ, Җом, Шим, Якш.
I decided to take the ones with 2 letters because they are used in the most of
calendars.
4. Yes, you were right. There were many mistakes there. I fixed it.
Please take a look at the new patch file.
I will try the filter.py script. Thank you!
With best wishes,
Mansur
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-03-15 21:28 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
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 [this message]
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-qJZCc3h2st@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).