public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "byrnejb@harte-lyne.ca" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug localedata/18408] New: Provide software utility to permit user created custom locales
Date: Wed, 13 May 2015 14:03:00 -0000	[thread overview]
Message-ID: <bug-18408-131@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 18408
           Summary: Provide software utility to permit user created custom
                    locales
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: localedata
          Assignee: unassigned at sourceware dot org
          Reporter: byrnejb@harte-lyne.ca
                CC: libc-locales at sourceware dot org
  Target Milestone: ---

A command line utility to permit user creation of and modification to valid
customised LOCALEs together with their proper installation and removal should
be provided with glibc.  The existing localedef utility is undocumented and
minimally useful for the installation of customised locales.  No useful editing
tool for locale definitions is provided at all.


See bugs: #9842 #12731 #16668

Editorial comment:

This whole situation with LOCALEs appears to me rather bizarre.  Surely the
date and time format an individual or group desire to employ on their own
computer systems should be their choice to make and not arbitrarily restrained
by the simple lack of suitable tools to do so.  Why is customising system
environmental information display made so difficult for end users to do for
themselves?

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


             reply	other threads:[~2015-05-13 14:03 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-13 14:03 byrnejb@harte-lyne.ca [this message]
2015-05-13 14:27 ` [Bug localedata/18408] " myllynen at redhat dot com
2015-05-13 14:38 ` schwab@linux-m68k.org
2015-05-13 15:02 ` byrnejb@harte-lyne.ca
2015-05-13 15:07 ` byrnejb@harte-lyne.ca
2015-05-15 12:04 ` myllynen at redhat dot com
2015-05-15 12:42 ` fweimer at redhat dot com
2015-05-15 14:46 ` byrnejb@harte-lyne.ca
2015-05-15 15:50 ` carlos at redhat dot com
2015-05-15 16:11 ` byrnejb@harte-lyne.ca
2015-05-15 16:18 ` byrnejb@harte-lyne.ca
2015-05-15 17:51 ` carlos at redhat dot com
2015-05-15 18:50 ` carlos at redhat dot com
2015-05-15 19:29 ` byrnejb@harte-lyne.ca
2015-05-15 19:33 ` byrnejb@harte-lyne.ca
2015-05-15 19:36 ` carlos at redhat dot com
2015-05-15 20:04 ` byrnejb@harte-lyne.ca
2015-05-15 20:07 ` carlos at redhat dot com
2015-05-15 20:42 ` byrnejb@harte-lyne.ca
2015-05-15 21:04 ` joseph at codesourcery dot com
2015-05-16 10:12 ` keld at keldix dot com
2015-06-22 13:13 ` myllynen at redhat dot com
2015-06-22 13:21 ` myllynen at redhat dot com
2015-06-22 18:13 ` byrnejb@harte-lyne.ca
2015-06-23 14:49 ` maiku.fabian at gmail dot com
2015-07-11 17:46 ` neleai at seznam dot cz
2015-08-27 22:00 ` [Bug locale/18408] " jsm28 at gcc dot gnu.org

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-18408-131@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: 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).