public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "maiku.fabian 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 11:18:53 +0000 [thread overview] Message-ID: <bug-31411-131-TsQD924rOO@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 #1 from Mike FABIAN <maiku.fabian at gmail dot com> --- (In reply to Rudolfs Mazurs from comment #0) > Created attachment 15377 [details] > 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?\ Yes. LC_COLLATE copy "lv_LV" END LC_COLLATE Several others can be copied from lv_LV as well as they are identical: LC_CTYPE copy "lv_LV" END LC_CTYPE LC_MONETARY copy "lv_LV" END LC_MONETARY LC_NUMERIC copy "lv_LV" END LC_NUMERIC LC_TELEPHONE copy "lv_LV" END LC_TELEPHONE LC_NAME copy "lv_LV" END LC_NAME > - 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. I don't know of any way to do that except using the LANGUAGE environment variable, i.e. you can use these settings: LANGUAGE=ltg:lv LANG=ltg_LV.UTF-8 See: https://www.gnu.org/software/gettext/manual/html_node/The-LANGUAGE-variable.html -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-06-11 11:18 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 [this message] 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 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-TsQD924rOO@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).