public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "egmont at uhulinux dot hu" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs@sources.redhat.com Subject: [Bug localedata/192] New: monthname abbrev more than 3 chars? Date: Mon, 31 May 2004 11:44:00 -0000 [thread overview] Message-ID: <20040531114356.192.egmont@uhulinux.hu> (raw) In Hungarian the official abbreviation of some monthnames are longer than 3 chars (4 or 5). Please see the attached patch. Is it right to have month name abbreviations that are longer than 3 chars in libc? It causes troubles in some applications, e.g. mc goes stupid, and listing within ncftp and "ls -l --time-style=locale" looks a bit silly. However, IMHO it's better if libc provides correct monthnames and the application does some workaround if it cannot handle more than three chars. Furthermore, if there existed a format string to strftime() which told to display %b in no more than 3 chars, it would help applications (e.g. mc). (Please consider this a feature request :-) -- Summary: monthname abbrev more than 3 chars? Product: glibc Version: 2.3.3 Status: NEW Severity: minor Priority: P2 Component: localedata AssignedTo: pere at hungry dot com ReportedBy: egmont at uhulinux dot hu CC: glibc-bugs at sources dot redhat dot com http://sources.redhat.com/bugzilla/show_bug.cgi?id=192 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2004-05-31 11:44 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-05-31 11:44 egmont at uhulinux dot hu [this message] 2004-05-31 11:44 ` [Bug localedata/192] " egmont at uhulinux dot hu 2004-07-21 7:25 ` pere at hungry dot com 2005-10-14 20:28 ` drepper at redhat dot com 2005-10-17 10:39 ` egmont at uhulinux dot hu 2006-05-01 17:55 ` drepper at redhat 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=20040531114356.192.egmont@uhulinux.hu \ --to=sourceware-bugzilla@sources.redhat.com \ --cc=glibc-bugs@sources.redhat.com \ /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).