public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "priest at johnromanodorazio dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/24366] la_VA locale support
Date: Mon, 20 Dec 2021 00:15:37 +0000	[thread overview]
Message-ID: <bug-24366-716-Gg0xhnYKsB@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24366-716@http.sourceware.org/bugzilla/>

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

John R. D'Orazio <priest at johnromanodorazio dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |priest at johnromanodorazio dot co
                   |                            |m

--- Comment #5 from John R. D'Orazio <priest at johnromanodorazio dot com> ---
I would second the addition of a Latin locale. I have been running into a few
issues in the past couple years as I develop some applications in PHP that have
strings in a number of languages, among which is Latin. However since there is
no Latin locale in the system, none of the strings in Latin can be handled
through `gettext` or any kind of localization functions in PHP (such as the
soon to be deprecated `strftime`, or the newer `IntlDateFormatter`, just to
mention a couple examples). Which means I can handle all translatable strings
through `gettext` with the exception of Latin, which I have to hardcode into my
applications. This makes for an application that becomes hard to maintain, it
would be so much easier to just be able to handle any Latin translations just
like any other language that is supported by the application.

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

  parent reply	other threads:[~2021-12-20  0:15 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
2021-12-20  0:15 ` priest at johnromanodorazio dot com [this message]
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-Gg0xhnYKsB@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).