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 locale/31411] New: Add Latgalian locale Date: Sat, 24 Feb 2024 15:53:20 +0000 [thread overview] Message-ID: <bug-31411-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31411 Bug ID: 31411 Summary: Add Latgalian locale Product: glibc Version: unspecified Status: UNCONFIRMED Severity: normal Priority: P2 Component: locale Assignee: unassigned at sourceware dot org Reporter: rudolfs.mazurs at gmail dot com Target Milestone: --- Created attachment 15377 --> https://sourceware.org/bugzilla/attachment.cgi?id=15377&action=edit Possible Latgalian locale file demo Glibc is missing the locale description for Latgalian (ltg). Latgalian locale is in process of being added to the CLDR: https://unicode-org.atlassian.net/browse/CLDR-2671 I have attached a possible implementation for the locale file. It is somewhat based on the Latvian locale file. I have not verified that the ltg_LV file is valid. Some things that would be nice to have, but I have no idea how to describe it in code: - Collation rules for Latvian (lv_LV) and Latgalian are the same. Is it possible to just use the Latvian rules, so that if someone reports a bug for the Latvian collation rules, they would automatically apply to the Latgalian? - Is there a way to designate Latvian locale as the fallback to the Latgalian locale? I mean, if the user chooses to use Latgalian translations, but for a given application there is no Latgalian translation, the system should try to use the Latvian translation before falling back to English. -- You are receiving this mail because: You are on the CC list for the bug.
reply other threads:[~2024-02-24 15:53 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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@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).