public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug localedata/23774] lv_LV collates Y/y incorrectly Date: Wed, 08 Sep 2021 15:12:24 +0000 [thread overview] Message-ID: <bug-23774-131-GjoPqhrCJC@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-23774-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=23774 Carlos O'Donell <carlos at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |carlos at redhat dot com Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED --- Comment #4 from Carlos O'Donell <carlos at redhat dot com> --- The notes from Mike indicate that this is not a bug in the glibc locale data for lv_LV and that we are harmonized with CLDR. I haven't seen further comments from Danko Alexeyev to refute that. I'm marking this RESOLVED NOTABUG. To answer Reinis Dane's question, yes you can make alternative collations, but they must be alternative locales e.g. lv_LV@alt1.utf8 where the "@alt1" to define a suffice for an alternative locale e.g. lv_LV@alt1 which has distinct collation from lv_LV. -- You are receiving this mail because: You are on the CC list for the bug.
next parent reply other threads:[~2021-09-08 15:12 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-23774-131@http.sourceware.org/bugzilla/> 2021-09-08 15:12 ` carlos at redhat dot com [this message] 2023-12-08 21:19 ` rudolfs.mazurs at gmail dot com 2024-02-01 22:10 ` rudolfs.mazurs at gmail dot com 2024-02-07 8:44 ` maiku.fabian at gmail dot com 2024-02-07 8:45 ` maiku.fabian at gmail dot com 2024-02-07 15:03 ` maiku.fabian at gmail dot com 2024-02-08 7: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-23774-131-GjoPqhrCJC@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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: linkBe 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).