From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/31411] Add Latgalian locale
Date: Mon, 17 Jun 2024 09:50:36 +0000 [thread overview]
Message-ID: <bug-31411-716-G6av0WC2wi@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31411-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31411
--- Comment #11 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Mike Fabian <mfabian@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=3ea79f50853afcbe17d6a4e2537e1bd5a2d17e7d
commit 3ea79f50853afcbe17d6a4e2537e1bd5a2d17e7d
Author: Mike FABIAN <mfabian@redhat.com>
Date: Mon Jun 10 19:54:42 2024 +0200
Define ISO 639-3 "ltg" (Latgalian) and add ltg_LV locale
Resolves: BZ # 31411
References:
https://iso639-3.sil.org/code/ltg
https://en.wikipedia.org/wiki/Latgalian_language
https://github.com/unicode-org/cldr/blob/main/common/main/ltg.xml
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-06-17 9:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-31411-716@http.sourceware.org/bugzilla/>
2024-06-11 10:54 ` maiku.fabian at gmail dot com
2024-06-11 11:18 ` maiku.fabian at gmail dot com
2024-06-11 11:39 ` maiku.fabian at gmail dot com
2024-06-11 11:42 ` maiku.fabian at gmail dot com
2024-06-11 11:59 ` maiku.fabian at gmail dot com
2024-06-11 20:45 ` rudolfs.mazurs at gmail dot com
2024-06-11 21:05 ` maiku.fabian at gmail dot com
2024-06-11 21:07 ` maiku.fabian at gmail dot com
2024-06-11 21:23 ` maiku.fabian at gmail dot com
2024-06-11 21:48 ` rudolfs.mazurs at gmail dot com
2024-06-12 7:14 ` maiku.fabian at gmail dot com
2024-06-17 9:50 ` cvs-commit at gcc dot gnu.org [this message]
2024-06-17 9:51 ` 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-31411-716-G6av0WC2wi@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).