From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/24369] Orthographic mistakes in 'mon' and 'abmon' sections in tt_RU (Tatar) locale
Date: Tue, 28 May 2019 20:17:00 -0000 [thread overview]
Message-ID: <bug-24369-716-7JyiJ2tdHv@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24369-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24369
--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Rafal Luzynski <rl@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=182a3746b8cc28784718c8ea27346e97d1423945
commit 182a3746b8cc28784718c8ea27346e97d1423945
Author: mansayk <6688000@gmail.com>
Date: Sat Mar 16 11:33:30 2019 +0300
tt_RU: Fix orthographic mistakes in mon and abmon sections [BZ #24369]
This commit fixes some errors and converts all month names to lowercase.
The content is synchronized with CLDR-35.1 now but trailing dots are
removed from abmon values in order to maintain consistency with the
previous values and with many other locales which do the same.
[BZ #24369]
* localedata/locales/tt_RU (mon): Update from CLDR-35.1, fix errors.
(abmon): Likewise, but remove the trailing dots.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-05-28 20:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 7:48 [Bug localedata/24369] New: " 6688000 at gmail dot com
2019-03-21 7:52 ` [Bug localedata/24369] " 6688000 at gmail dot com
2019-05-28 20:17 ` cvs-commit at gcc dot gnu.org [this message]
2019-05-28 20:36 ` digitalfreak at lingonborough dot com
2019-05-28 21:45 ` digitalfreak at lingonborough dot com
2019-05-29 8:07 ` 6688000 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-24369-716-7JyiJ2tdHv@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).