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/22527] tr_TR  LC_COLLATE does not use copy "iso14651_t1"
Date: Mon, 04 Dec 2017 17:36:00 -0000	[thread overview]
Message-ID: <bug-22527-716-luCAbxH6AP@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22527-716@http.sourceware.org/bugzilla/>

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

--- Comment #1 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  96b06a19e602557bfa668ad9c1a9f29044d3e774 (commit)
       via  1f6d91f328b7699610210d7d56d2cc49d60e1c27 (commit)
      from  2e49fed84c9ada0ad54445d197060dc28ee94103 (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=96b06a19e602557bfa668ad9c1a9f29044d3e774

commit 96b06a19e602557bfa668ad9c1a9f29044d3e774
Author: Mike FABIAN <mfabian@redhat.com>
Date:   Mon Dec 4 17:46:28 2017 +0100

    tr_TR locale: Base collation on iso14651_t1 [BZ #22527]

        [BZ #22527]
        *  localedata/locales/tr_TR (LC_COLLATE): Base collation rules
        on iso14651_t1. A test file localedata/tr_TR.UTF-8.in is already
        available, this rewrite of the collation rules does reproduce
        the test file in the same order.

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=1f6d91f328b7699610210d7d56d2cc49d60e1c27

commit 1f6d91f328b7699610210d7d56d2cc49d60e1c27
Author: Mike FABIAN <mfabian@redhat.com>
Date:   Mon Dec 4 13:10:29 2017 +0100

    hr_HR locale: Don’t use single code points for the digraphs in LC_TIME

        [BZ #10580]
        * localedata/locales/hr_HR (LC_TIME): Use two letters for the
        digraphs in the month and day names. Using single code points for
        digraphs is deprecated.  While there are dedicated Unicode
        codepoints, for the digraphs, these are included for backwards
        compatibility and modern texts use a sequence of Basic Latin
        characters. See: https://www.unicode.org/faq/ligature_digraph.html
        This makes the month and day names agree exactly with CLDR now,
        CLDR does not use the single code points for the digraphs either.

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

Summary of changes:
 ChangeLog                |   20 +
 localedata/locales/hr_HR |   18 +-
 localedata/locales/tr_TR | 2112 ++--------------------------------------------
 3 files changed, 82 insertions(+), 2068 deletions(-)

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

  parent reply	other threads:[~2017-12-04 17:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-29 12:57 [Bug localedata/22527] New: " maiku.fabian at gmail dot com
2017-11-29 12:57 ` [Bug localedata/22527] " maiku.fabian at gmail dot com
2017-12-04 17:36 ` cvs-commit at gcc dot gnu.org [this message]
2017-12-04 17:38 ` maiku.fabian 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-22527-716-luCAbxH6AP@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).