public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bugdal at aerifal dot cx" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug localedata/14641] Add a strftime()-like function for formatting human names Date: Fri, 28 Sep 2012 12:21:00 -0000 [thread overview] Message-ID: <bug-14641-131-6MPpDubBRN@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-14641-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=14641 Rich Felker <bugdal at aerifal dot cx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bugdal at aerifal dot cx --- Comment #2 from Rich Felker <bugdal at aerifal dot cx> 2012-09-28 12:21:06 UTC --- I think this feature is fundamentally misguided. There is no universal way to represent a "broken down" human name; the whole "first name last name" or "family name" concept is rooted in particular cultures and does not even apply to others. I don't think glibc has any business perpetuating the concept that it's reasonable for applications to store names like this. Properly written applications should simply be storing a single "name" field as one string, possibly tagged with a subrange of the string to be used as a primary sort key. Other useful tagging would be rules specific to the named persons' culture for how to transform their name into a salutation, etc. But this is specific to the culture of the person being named, not the locale. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2012-09-28 12:21 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-28 11:33 [Bug localedata/14641] New: " bugzilla at tecnocode dot co.uk 2012-09-28 12:06 ` [Bug localedata/14641] " keld at keldix dot com 2012-09-28 12:21 ` bugdal at aerifal dot cx [this message] 2013-11-06 12:54 ` simon.mcvittie at collabora dot co.uk 2013-11-06 15:11 ` bugdal at aerifal dot cx 2013-11-06 16:10 ` simon.mcvittie at collabora dot co.uk 2013-11-06 20:33 ` Ondřej Bílka 2013-11-06 16:32 ` bugdal at aerifal dot cx 2013-11-06 20:35 ` neleai at seznam dot cz 2013-11-06 23:57 ` keld at keldix dot com 2013-11-07 2:26 ` bugdal at aerifal dot cx 2013-11-07 15:00 ` bugdal at aerifal dot cx 2013-11-07 19:02 ` keld at keldix dot com 2014-06-17 4:17 ` fweimer at redhat dot com 2014-06-17 7:32 ` [Bug localedata/14641] Deprecate name_fmt bugzilla at tecnocode dot co.uk 2014-06-17 7:48 ` fweimer at redhat dot com 2014-06-17 16:55 ` keld at keldix dot com 2014-06-17 17:08 ` bugdal at aerifal dot cx 2014-06-19 22:47 ` bugzilla at tecnocode dot co.uk 2014-06-20 5:48 ` keld at keldix dot com 2014-06-20 6:16 ` bugdal at aerifal dot cx 2014-06-20 11:04 ` keld at keldix dot com 2014-06-20 13:01 ` bugzilla at tecnocode dot co.uk 2014-06-21 18:36 ` keld at keldix dot com 2014-06-23 7:44 ` fweimer at redhat dot com 2014-06-23 13:02 ` keld at keldix dot com 2014-06-23 15:42 ` myllynen at redhat dot com 2014-06-23 21:07 ` keld at keldix dot com 2014-06-23 21:20 ` bugdal at aerifal dot cx 2014-06-23 22:13 ` keld at keldix dot com 2014-06-24 7:38 ` fweimer 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=bug-14641-131-6MPpDubBRN@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --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).