From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9AB353858D34; Tue, 11 Jun 2024 11:18:53 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9AB353858D34 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1718104733; bh=npY3BjkUP2tOj1sDW07mGwilOIlJIwJj1fMtN1EsUkM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=wlHzMirPjBrTuGaItDQqBnr2f47ZZkvmpGX0v5b2sM11SHwhUm9m4RJP2kBcpNYvZ Azl+Q5gv4DKQhTIY4z2XCpHa2ffGocJ8DJNpjxFCyQq7pnO3+hJKyfugNkIaQCx2W9 UeWpvs5MeElp7ztTY23YoQPD8zOnbZbTPw7Vn4Wc= From: "maiku.fabian at gmail dot com" To: glibc-bugs@sourceware.org Subject: [Bug localedata/31411] Add Latgalian locale Date: Tue, 11 Jun 2024 11:18:53 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: localedata X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: maiku.fabian at gmail dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: maiku.fabian at gmail dot com X-Bugzilla-Target-Milestone: 2.40 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D31411 --- Comment #1 from Mike FABIAN --- (In reply to Rudolfs Mazurs from comment #0) > Created attachment 15377 [details] > Possible Latgalian locale file demo >=20 > Glibc is missing the locale description for Latgalian (ltg). >=20 > Latgalian locale is in process of being added to the CLDR: > https://unicode-org.atlassian.net/browse/CLDR-2671 >=20 > 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. >=20 > Some things that would be nice to have, but I have no idea how to describe > it in code: >=20 > - 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 Latgal= ian?\ 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 translatio= ns, > 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=3Dltg:lv LANG=3Dltg_LV.UTF-8 See: https://www.gnu.org/software/gettext/manual/html_node/The-LANGUAGE-variable= .html --=20 You are receiving this mail because: You are on the CC list for the bug.=