From: "6688000 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/24296] New: Orthographic mistakes in 'day' and 'abday' sections in tt_RU (Tatar) locale
Date: Sun, 03 Mar 2019 10:37:00 -0000 [thread overview]
Message-ID: <bug-24296-716@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=24296
Bug ID: 24296
Summary: Orthographic mistakes in 'day' and 'abday' sections in
tt_RU (Tatar) locale
Product: glibc
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: localedata
Assignee: unassigned at sourceware dot org
Reporter: 6688000 at gmail dot com
CC: libc-locales at sourceware dot org
Target Milestone: ---
Created attachment 11660
--> https://sourceware.org/bugzilla/attachment.cgi?id=11660&action=edit
A patch file with suggested corrections.
Hello!
tt_RU (Tatar language) locale.
There are three orthographic mistakes in 'day' section:
'Дышәмбе' should be 'Дүшәмбе'
'Чәршәәмбе' should be 'Чәршәмбе'
'Пәнҗешмбе' should be 'Пәнҗешәмбе'
and one typo in 'abday' section:
'Дыш' should be 'Дүш'
WRONG:
$ LANG=tt_RU locale day
Якшәмбе;Дышәмбе;Сишәмбе;Чәршәәмбе;Пәнҗешмбе;Җомга;Шимбә
$ LANG=tt_RU locale abday
Якш;Дыш;Сиш;Чәрш;Пәнҗ;Җом;Шим
CORRECT:
$ LANG=tt_RU locale day
Якшәмбе;Дүшәмбе;Сишәмбе;Чәршәмбе;Пәнҗешәмбе;Җомга;Шимбә
$ LANG=tt_RU locale abday
Якш;Дүш;Сиш;Чәрш;Пәнҗ;Җом;Шим
I attach a patch file with corresponding corrections.
Correctness of suggested changes can be proved by:
Unicode.org CLDR Charts:
https://www.unicode.org/cldr/charts/34/summary/tt.html
Academic dictionaries of Tatar language:
http://suzlek.antat.ru/
Thank you!
With best wishes,
Mansur
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-03-03 10:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-03 10:37 6688000 at gmail dot com [this message]
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
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@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).