public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "bugdal at aerifal dot cx" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/14641] Add a strftime()-like function for formatting human names
Date: Wed, 06 Nov 2013 16:33:00 -0000	[thread overview]
Message-ID: <bug-14641-716-tGSegVveY0@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14641-716@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=14641

--- Comment #6 from Rich Felker <bugdal at aerifal dot cx> ---
On Wed, Nov 06, 2013 at 04:08:37PM +0000, simon.mcvittie at collabora dot co.uk
wrote:
> OK, so is your position that _NL_NAME_NAME_FMT should never be used, and if we
> need similar functionality, we should invent our own?

My opinion on this is not authoritative for glibc, but yes, my
position is that this locale property should be considered deprecated
and that new features using it should not be added. My reasoning is
that treating name formatting as a property of the user's locale is
fundamentally wrong. The way you format a person's name is a function
of _their_ cultural conventions, not your cultural conventions. Since
libc's locale system does not and cannot know the conventions
associated with the name being formatted, it cannot help you get the
correct results.

In some sense, _NL_NAME_NAME_FMT is less of an offense because it
might help programs know the right formatting (or a right default to
try) for new names introduced by the user. If a program takes the
format string and does its own formatting, it can also accept other
non-default formats. But if a program requests that the libc do the
formatting based on the current locale, there is no way to handle
non-default formats. In this sense, I would object less to a function
like strftime for names that took the name format string as an
explicit argument, rather than using the current locale's format
string. This is certainly an option that could be proposed and
discussed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2013-11-06 16:33 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-28 11:50 [Bug localedata/14641] New: " bugzilla at tecnocode dot co.uk
2012-09-28 12:05 ` Keld Simonsen
2012-09-28 12:41 ` [Bug localedata/14641] " keld at keldix dot com
2012-09-28 12:41 ` bugdal at aerifal dot cx
2013-11-06 13:01 ` simon.mcvittie at collabora dot co.uk
2013-11-06 15:13 ` bugdal at aerifal dot cx
2013-11-06 16:12 ` simon.mcvittie at collabora dot co.uk
2013-11-06 16:33 ` bugdal at aerifal dot cx [this message]
2013-11-06 23:57   ` Keld Simonsen
2013-11-06 23:58 ` keld at keldix dot com
2013-11-06 23:58 ` neleai at seznam dot cz
2013-11-07  3:16 ` bugdal at aerifal dot cx
2013-11-07 12:29   ` Keld Simonsen
2013-11-07 12:30 ` keld at keldix dot com
2013-11-07 15:27 ` bugdal at aerifal dot cx
2013-11-07 19:02   ` Keld Simonsen
2013-11-07 19:03 ` keld at keldix dot com
2014-06-17  4:30 ` fweimer at redhat dot com
2014-06-17  7:33 ` [Bug localedata/14641] Deprecate name_fmt bugzilla at tecnocode dot co.uk
2014-06-17  7:49 ` fweimer at redhat dot com
2014-06-17 16:54   ` Keld Simonsen
2014-06-17 17:03 ` keld at keldix dot com
2014-06-17 17:09 ` bugdal at aerifal dot cx
2014-06-20  5:48   ` Keld Simonsen
2014-06-19 22:48 ` bugzilla at tecnocode dot co.uk
2014-06-20  5:50 ` keld at keldix dot com
2014-06-20  7:28 ` bugdal at aerifal dot cx
2014-06-20 11:03   ` Keld Simonsen
2014-06-20 11:05 ` keld at keldix dot com
2014-06-20 13:22 ` bugzilla at tecnocode dot co.uk
2014-06-21 18:35   ` Keld Simonsen
2014-06-21 18:37 ` keld at keldix dot com
2014-06-23  8:21 ` fweimer at redhat dot com
2014-06-23 13:01   ` Keld Simonsen
2014-06-23 13:04 ` keld at keldix dot com
2014-06-23 21:07   ` Keld Simonsen
2014-06-23 21:08 ` keld at keldix dot com
2014-06-23 21:08 ` myllynen at redhat dot com
2014-06-23 21:57 ` bugdal at aerifal dot cx
2014-06-23 22:12   ` Keld Simonsen
2014-06-23 22:13 ` keld at keldix dot com
2014-06-24  7:40 ` fweimer at redhat dot com
2016-02-19 10:46 ` [Bug localedata/14641] LC_NAME: deprecate locale category vapier at gentoo dot org
2016-02-19 15:42 ` myllynen at redhat dot com
2016-02-19 16:15 ` vapier at gentoo dot org
2016-02-19 18:29   ` Keld Simonsen
2016-02-19 18:33 ` keld at keldix dot com
2016-02-19 23:22 ` vapier at gentoo dot org
2016-02-19 23:26   ` Keld Simonsen
2016-02-19 23:27 ` keld at keldix dot com
2016-02-20  6:07 ` vapier at gentoo dot org
2016-02-22  8:10   ` Keld Simonsen
2016-02-22  8:12 ` keld at keldix dot com
2016-02-22 10:13 ` vapier at gentoo dot org
2019-01-02 11:59   ` Keld Simonsen
2018-12-20  8:38 ` pander at users dot sourceforge.net
2018-12-20  9:52 ` pander at users dot sourceforge.net
2019-01-01 11:42 ` pander at users dot sourceforge.net
2019-01-02 11:59 ` keld at keldix 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-716-tGSegVveY0@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=libc-locales@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).