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] New: la_VA locale support
Date: Wed, 20 Mar 2019 15:25:00 -0000	[thread overview]
Message-ID: <bug-24366-716@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 24366
           Summary: la_VA locale support
           Product: glibc
           Version: unspecified
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P2
         Component: localedata
          Assignee: unassigned at sourceware dot org
          Reporter: nicolalucasbuescher+bugzilla at gmail dot com
                CC: libc-locales at sourceware dot org
  Target Milestone: ---

Currently, there is no locale support for Latin (la_VA) in glibc. Since, iirc,
the address, date, time, etc info for the Vatican is identical to those for
Italy, this can easily be created based on the it_IT locale definition, with
minor changes for the language and country.

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

             reply	other threads:[~2019-03-20 15:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-20 15:25 nicolalucasbuescher+bugzilla at gmail dot com [this message]
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
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@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).