public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <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: Wed, 20 Mar 2019 21:05:00 -0000	[thread overview]
Message-ID: <bug-24296-716-fVM8ltqNFW@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24296-716@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=24296

--- Comment #12 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".

The branch, master has been updated
       via  57ada43c905eec7ba28fe60a08b93a52d88e26c1 (commit)
      from  a2e57f89a35e6056c9488428e68c4889e114ef71 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=57ada43c905eec7ba28fe60a08b93a52d88e26c1

commit 57ada43c905eec7ba28fe60a08b93a52d88e26c1
Author: mansayk <6688000@gmail.com>
Date:   Sat Mar 16 11:05:22 2019 +0300

    tt_RU: Fix orthographic mistakes in day and abday sections [BZ #24296]

    This commit fixes some errors and converts all weekday names to lowercase.
    The content is synchronized with CLDR-34 now, but trailing dots are removed
    from abday values in order to maintain consistency with the previous values
    and with many other locales which do the same.

        [BZ #24296]
        * localedata/locales/tt_RU (day): Update from CLDR-34, fix errors.
        (abday): Likewise, but remove the trailing dots.

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog                |    6 ++++++
 localedata/locales/tt_RU |   28 ++++++++++++++--------------
 2 files changed, 20 insertions(+), 14 deletions(-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2019-03-20 21:05 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
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 [this message]
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-fVM8ltqNFW@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).