public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "priest at johnromanodorazio dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug localedata/24366] la_VA locale support Date: Tue, 21 Dec 2021 11:02:12 +0000 [thread overview] Message-ID: <bug-24366-131-yuVmwuMfih@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-24366-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=24366 --- Comment #7 from John R. D'Orazio <priest at johnromanodorazio dot com> --- I'm also seeing that there has been some activity on CLDR for a definition of Latin among supported locales: https://github.com/unicode-org/cldr/blob/main/seed/main/la.xml However, I see that Ancient / Classical Latin has been used rather than Ecclesiastical Latin in some cases in the proposed definition. I'm checking in with the Pontifical Academy for the Latin Language ( https://www.pontificiaacademialatinitatis.org/ ) and with other academic resources such as the Pontifical Institute for Higher Latin at the Salesian University in Rome, for a consultation, so as to propose a correct definition that will be useful for modern uses. If I have any updates from this consultation, I will post them here. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-12-21 11:02 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-24366-131@http.sourceware.org/bugzilla/> 2020-05-15 15:55 ` nicolalucasbuescher+bugzilla at gmail dot com 2021-12-20 0:15 ` priest at johnromanodorazio dot com 2021-12-20 3:45 ` priest at johnromanodorazio dot com 2021-12-21 11:02 ` priest at johnromanodorazio dot com [this message] 2024-01-18 11:00 ` maiku.fabian at gmail dot com 2024-01-18 13:40 ` priest at johnromanodorazio 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-24366-131-yuVmwuMfih@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).