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/25324] lv_LV: d_t_fmt contains suspicious words in the time part
Date: Mon, 30 Dec 2019 10:51:00 -0000	[thread overview]
Message-ID: <bug-25324-716-tPdussqU6f@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25324-716@http.sourceware.org/bugzilla/>

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

--- 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=d99b500e3da713416ee8bff8f3f9799411c811a2

commit d99b500e3da713416ee8bff8f3f9799411c811a2
Author: Rafał Lużyński <digitalfreak@lingonborough.com>
Date:   Mon Dec 30 11:42:46 2019 +0100

    lv_LV locale: Correct the time part of d_t_fmt (bug 25324)

    Currently d_t_fmt formats time as "plkst. %H un %M".  A quick Google
    search says that "plkst." means "o’clock" and "un" means "and".
    Also this format does not display seconds.

    CLDR does not mention anything like that.  We have no reason to use
    anything different than "%H:%M:%S".

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

  reply	other threads:[~2019-12-30 10:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-30 10:43 [Bug localedata/25324] New: " digitalfreak at lingonborough dot com
2019-12-30 10:51 ` cvs-commit at gcc dot gnu.org [this message]
2019-12-30 10:57 ` [Bug localedata/25324] " digitalfreak at lingonborough dot com
2019-12-30 20:09 ` 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-25324-716-tPdussqU6f@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).