public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
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 13:13:00 -0000 [thread overview] Message-ID: <bug-18408-131-ZZ6e6oCdcz@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 #23 from Marko Myllynen <myllynen at redhat dot com> --- > So all anyone need do to create a custom locale file is to: > > What could be simpler? After all, it did not take me much more than four or > five days to figure this all out on my own. I have probably forgotten a > number of other steps that were also necessary and so are not listed here. I would imagine anyone interested in this area will either do a web search for something "glibc locale" or just type "man locale." Both of these methods today lead to the following interlinked documents which should provide all the information needed so while there's still lots of manual work to do, at least it should be easier to see what needs to be done. https://sourceware.org/glibc/wiki/Locales http://man7.org/linux/man-pages/man1/locale.1.html http://man7.org/linux/man-pages/man5/locale.5.html http://man7.org/linux/man-pages/man7/locale.7.html http://man7.org/linux/man-pages/man1/localedef.1.html The missing reference to strftime(3) was a fair point and it has now been fixed in upstream: http://git.kernel.org/cgit/docs/man-pages/man-pages.git/commit/?id=ea7208a6aae62dbe7af43a21654d2d269ca41957 > At the very least we need: > > * localedef documentation. > * examples using localedef to install a locale to the locale archive. 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? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2015-06-22 13: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 [this message] 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-ZZ6e6oCdcz@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).