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/25044] Incorrect days of the week abbreviation (abday) in ru_UA locale
Date: Tue, 26 Nov 2019 11:02:00 -0000	[thread overview]
Message-ID: <bug-25044-716-MW6WRSEys5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25044-716@http.sourceware.org/bugzilla/>

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

--- Comment #1 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=c372d2e863075cbc4b24141743026954b6e2457e

commit c372d2e863075cbc4b24141743026954b6e2457e
Author: Rafał Lużyński <digitalfreak@lingonborough.com>
Date:   Tue Oct 1 22:11:47 2019 +0200

    ru_UA locale: use copy "ru_RU" in LC_TIME (bug 25044)

    Replacing incorrect abbreviated weekday names "Пнд", "Вто", "Срд"...
    with correct ones "Пн", "Вт", "Ср"... makes the LC_TIME sections in
    those two locales almost identical.  The only remaining difference
    was that ab_alt_mon elements in ru_UA were lowercase while in ru_RU
    they had the first letter uppercase, the latter was pointed as
    a better choice by a native speaker.  This commit unifies LC_TIME
    between ru_RU and ru_UA.

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

  reply	other threads:[~2019-11-26 11:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-28  6:51 [Bug localedata/25044] New: " mikhail.gribanov at gmail dot com
2019-11-26 11:02 ` cvs-commit at gcc dot gnu.org [this message]
2019-11-26 11:05 ` [Bug localedata/25044] " digitalfreak at lingonborough dot com
2020-07-08 16:45 ` jsm28 at gcc dot gnu.org

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-25044-716-MW6WRSEys5@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).