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] Add a strftime()-like function for formatting human names
Date: Thu, 07 Nov 2013 15:00:00 -0000	[thread overview]
Message-ID: <bug-14641-131-H3knT6lrI7@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14641-131@http.sourceware.org/bugzilla/>

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

--- Comment #11 from Rich Felker <bugdal at aerifal dot cx> ---
On Thu, Nov 07, 2013 at 12:29:55PM +0000, keld at keldix dot com wrote:
> If there are different users then it is only natural to switch to each user's
> locale, eg when printing a name, or printing an address.

No. Locale names (and whether they even exist) are
implementation-defined. A correct application cannot use locales by
name, but can only use the user's configured locale or the C/POSIX
locale. Applications which assume the existence of particular locale
names are not portable, and even if you only cared about them working
on GNU/Linux systems, many such desktop systems only have one locale
installed (the user's own locale).

Even if you could assume the names and existence of locales, their
definitions may vary slightly between systems, which means the
interpretation of your data would not be portable. The key here is
that name "formatting" is not just presentation, it's actually
interpretation.

> I believe this is in scope of libc, meaning that this is to make an application
> culturally adaptable. It is just a more advanced use than the normal i18n,
> because we want to accomodate different users' cultural conventions.

No, the cultural conventions in question are not cultural conventions
of any users of the system. The data you're working with has been
encoded (I would go so far as to say "corrupted") in a way that's
dependent on the cultural conventions of the person whom it names (or
sometimes not even that, but the cultural conventions imposed on that
person by virtue of where they're living and their legal status
there). The problem is decoding it to the person's actual name.

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


  parent reply	other threads:[~2013-11-07 15:00 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
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 [this message]
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-H3knT6lrI7@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).