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/24054] Many locales are missing date_fmt
Date: Thu, 02 Jan 2020 10:52:00 -0000	[thread overview]
Message-ID: <bug-24054-716-T7SzkSkLtS@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24054-716@http.sourceware.org/bugzilla/>

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

--- 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=75ba929987f6950dd008ef0f6270f1b21e9af511

commit 75ba929987f6950dd008ef0f6270f1b21e9af511
Author: Rafał Lużyński <digitalfreak@lingonborough.com>
Date:   Mon Dec 30 11:58:18 2019 +0100

    Multiple locales: Add date_fmt (bug 24054)

    It is not specified what should be the content of d_t_fmt and date_fmt
    but in the built-in C locale those fields have only one difference:
    date_fmt contains "%Z" (the current time zone) while d_t_fmt does not.

    For most of the locales this commit does the following operation:
    copy d_t_fmt to date_fmt, and then remove "%Z" from d_t_fmt.
    If "%Z" was originally missing from d_t_fmt add it to date_fmt.
    It also corrects comments where necessary.

    Exceptions:

    * In bo_CN, dz_BT, and km_KH "%Z" has not been added to date_fmt because
      it was too difficult.  In these locales date_fmt has been set to the
      copy of d_t_fmt.
    * In en_DK "%Z" has not been removed from d_t_fmt in order to preserve
      the conformance with the standard mentioned in the comment.

    The command to identify and initially edit the locales that need the
    update was:

        for i in `grep -lw d_t_fmt *`
        do
            if ! grep -qw date_fmt $i ; then
                awk '/d_t_fmt/ { print $0; gsub("d_t_fmt", "date_fmt"); } //{
print $0 }' < $i > $i.next
                mv $i.next $i
            fi
        done

    and then each file was further edited manually.

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

  parent reply	other threads:[~2020-01-02 10:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-02 17:41 [Bug localedata/24054] New: May " aurelien at aurel32 dot net
2019-01-02 18:03 ` [Bug localedata/24054] Many " aurelien at aurel32 dot net
2020-01-02 10:52 ` cvs-commit at gcc dot gnu.org [this message]
2020-01-02 10:53 ` 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-24054-716-T7SzkSkLtS@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).