public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "nicolalucasbuescher+bugzilla at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/24366] la_VA locale support
Date: Fri, 15 May 2020 15:55:18 +0000	[thread overview]
Message-ID: <bug-24366-716-yCyrWDys30@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24366-716@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=24366

--- Comment #4 from nicolalucasbuescher+bugzilla at gmail dot com ---
Rafal, that's certainly a fair point. My point of reference is that, while it
may or may not be appropriate to compare the feature set of Linux to other OSs,
in both macOS and Windows 10 you are able to set your locale/language to Latin
(lingua latina). In both cases, the setting applies only to the locale used for
applications, and Latin is not provided as a display language (what I would
call a second-class locale). But this enables applications to support Latin as
a language option.

Technically you can also do this in Linux without explicit glibc support, and I
did, but the fact that there is no actual locale file crashes some programs,
Dropbox being one. This fact that apps can actually crash is the reason I filed
a bug.

I'm not deeply familiar with how locales work in Linux, but my thought was that
having an la_VA locale would enable applications to support the language for
spell-checking, which I think would be a very good use-case for the locale,
considering that many many people still work with Latin, even though there are
no native speakers.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-05-15 15:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-20 15:25 [Bug localedata/24366] New: " nicolalucasbuescher+bugzilla at gmail dot com
2019-03-28 15:25 ` [Bug localedata/24366] " nicolalucasbuescher+bugzilla at gmail dot com
2019-12-29 13:41 ` jakub at redhat dot com
2020-01-09 23:44 ` digitalfreak at lingonborough dot com
2020-05-15 15:55 ` nicolalucasbuescher+bugzilla at gmail dot com [this message]
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
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-716-yCyrWDys30@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=libc-locales@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: link
Be 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).