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] Provide software utility to permit user created custom locales Date: Mon, 22 Jun 2015 18:13:00 -0000 [thread overview] Message-ID: <bug-18408-131-JJ6sLDFYW4@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-18408-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=18408 --- Comment #25 from James B. Byrne <byrnejb@harte-lyne.ca> --- On Mon, June 22, 2015 09:12, myllynen at redhat dot com wrote: > > These should already be covered by localedef(1) and other pages, > if you think something is missing perhaps you could describe the > issue in detail or even provide a patch / adjust the wiki page? > This is the current man page that ships with my distro, CentOS-6. As you can see there is no reference to glibc or to localedef. The point being is that without prior knowledge of the relationship between LOCALE and these other elements there is no clue to a researcher as to where to look further. I searched Google quite extensively to discover the bare existence of localedef. But when I searched for a man page for it all I could find was some private effort at an unofficial version, the reference to I have since misplaced. But, that page did point me to this: http://pubs.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap07.html#tag_07_03 Further, I note that the references you now helpfully provide are all dated as of December 2014 or later. Which, strangely enough, postdates my original reports on this matter by a little over two years. One might be forgiven in surmising that perhaps the availability of these documents in their current form is a consequence thereof rather than a failure to initially search for them. However, the entire process of establishing on Linux what is fundamentally a user preference is Byzantine to the point of ludicrous. LOCALE(1) LOCALE(1) NAME locale - Get locale-specific information. SYNOPSIS locale [ -a │ -m] locale [ -ck ] name... DESCRIPTION The locale program writes information about the current locale environment, or all locales, to standard output. When invoked without arguments, locale summarizes the current locale environment for each locale category defined by the LC_* environment variables. -a, --all-locales Write names of available locales. -m, --charmaps Write names of available charmaps. Output Format: -c, --category-name Write names of selected categories. -k, --keyword-name Write names and values of selected keywords. ENVIRONMENT VARIABLES LC_CTYPE Character classification and case conversion. LC_COLLATE Collation order. LC_TIME Date and time formats. LC_NUMERIC Non-monetary numeric formats. LC_MONETARY Monetary formats. LC_MESSAGES Formats of informative and diagnostic messages and interactive responses. AUTHOR locale is written by Ulrich Drepper for the GNU C Library. This manpage is written by Joel Klecker <espy@debian.org> for the Debian GNU/Linux system. 3rd Berkeley Distribution March 2001 LOCALE(1) -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-28624-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon Jun 22 18:31:29 2015 Return-Path: <glibc-bugs-return-28624-listarch-glibc-bugs=sources.redhat.com@sourceware.org> Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 34673 invoked by alias); 22 Jun 2015 18:31:29 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: <glibc-bugs.sourceware.org> List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org> List-Post: <mailto:glibc-bugs@sourceware.org> List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs> Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 34608 invoked by uid 48); 22 Jun 2015 18:31:25 -0000 From: "myllynen at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug localedata/18408] Provide software utility to permit user created custom locales Date: Mon, 22 Jun 2015 18:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: localedata X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: myllynen at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: Message-ID: <bug-18408-131-MeUNOKFDFg@http.sourceware.org/bugzilla/> In-Reply-To: <bug-18408-131@http.sourceware.org/bugzilla/> References: <bug-18408-131@http.sourceware.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-06/txt/msg00235.txt.bz2 Content-length: 889 https://sourceware.org/bugzilla/show_bug.cgi?id\x18408 --- Comment #26 from Marko Myllynen <myllynen at redhat dot com> --- (In reply to James B. Byrne from comment #25) > On Mon, June 22, 2015 09:12, myllynen at redhat dot com wrote: > > > > These should already be covered by localedef(1) and other pages, > > if you think something is missing perhaps you could describe the > > issue in detail or even provide a patch / adjust the wiki page? > > This is the current man page that ships with my distro, CentOS-6. As you > can see there is no reference to glibc or to localedef. My point was to illustrate that things have gotten better since, I know how unhelpful RHEL 6 / CentOS 6 locale related man pages, after all it was my main system when I worked to have proper localedef(1) included in upstream. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2015-06-22 18:13 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-13 14:03 [Bug localedata/18408] New: " byrnejb@harte-lyne.ca 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 [this message] 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-JJ6sLDFYW4@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).