public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rudolfs.mazurs at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug localedata/31411] Add Latgalian locale Date: Tue, 11 Jun 2024 21:48:15 +0000 [thread overview] Message-ID: <bug-31411-131-R1cyAMlZc2@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31411-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31411 --- Comment #9 from Rudolfs Mazurs <rudolfs.mazurs at gmail dot com> --- It looks like the current lv_LV and ltg_LV formats are "narrow" and what you propose is to use the "short" version. The LVS 1993:24 standard lists both formats as equally valid, so it's up to you. > So probably I should sync this part of the lv_LV locale to CLDR > abday "Sv";"Pr";/ > "Ot";"Tr";/ > "Ce";"Pk";/ > "Se" > and in the ltg_LV locale use > abday "Sv";"Pi";/ > "Ūt";"Tr";/ > "Ca";"Pk";/ > "Sa" This looks good to me. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-06-11 21:48 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-24 15:53 [Bug locale/31411] New: " rudolfs.mazurs at gmail dot com 2024-06-11 10:54 ` [Bug localedata/31411] " 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 [this message] 2024-06-12 7:14 ` maiku.fabian at gmail dot com 2024-06-17 9:50 ` cvs-commit at gcc dot gnu.org 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-131-R1cyAMlZc2@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).