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@sourceware.org
Subject: [Bug localedata/14641] Deprecate name_fmt
Date: Fri, 20 Jun 2014 06:16:00 -0000 [thread overview]
Message-ID: <bug-14641-131-uWXvNaX25m@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14641-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=14641
--- Comment #20 from Rich Felker <bugdal at aerifal dot cx> ---
On Fri, Jun 20, 2014 at 05:48:35AM +0000, keld at keldix dot com wrote:
> The LC_NAME (and LC_ADDTESS) category addresses a real need for providing
> culturally acceptable software. Really many cultures use the Family name,
> first name convention, which is offending to me for my name. The world is
> rather
> split in two halves on the order of given name and family name.
That's the naive and mistaken view that resulted in the creation of
LC_NAME/name_fmt to begin with. In reality there are a lot more
conventions than just these two, but the prevalence of information
systems that require names to be stored as a first/given name and a
last/family name seems to have made their existence much less visible.
Here are some other cultural conventions:
- Only one name. Attempting to force these into a given/family pattern
is offensive and results in things like being assigned a "first
name" of "FNU" and having your given name treated as a family name.
- Multiple names, but all given. Attempting to force these into a
given/family pattern is almost always offensive because it will
result in things like "Mr./Ms. Second-name", presenting a name
backwards as "Second-name First-name", etc.
- Multiple family names. I don't even know how this is typically
handled.
Wikipedia has some detailed coverage of the issues:
http://en.wikipedia.org/wiki/Family_name
http://en.wikipedia.org/wiki/Mononymous_person
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-06-20 6:16 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 11:33 [Bug localedata/14641] New: Add a strftime()-like function for formatting human names 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
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 [this message]
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-uWXvNaX25m@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).