From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15606 invoked by alias); 20 Jun 2014 11:03:48 -0000 Mailing-List: contact libc-locales-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: libc-locales-owner@sourceware.org Received: (qmail 15580 invoked by uid 89); 20 Jun 2014 11:03:47 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.6 required=5.0 tests=AWL,BAYES_00,KHOP_DYNAMIC,RCVD_IN_RP_RNBL,RDNS_DYNAMIC autolearn=no version=3.3.2 X-Spam-User: qpsmtpd, 2 recipients X-HELO: rap.rap.dk Date: Fri, 20 Jun 2014 11:03:00 -0000 From: Keld Simonsen To: bugdal at aerifal dot cx Cc: libc-locales@sourceware.org Subject: Re: [Bug localedata/14641] Deprecate name_fmt Message-ID: <20140620110342.GA7170@rap.rap.dk> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-SW-Source: 2014-q2/txt/msg00189.txt.bz2 On Fri, Jun 20, 2014 at 06:16:42AM +0000, bugdal at aerifal dot cx wrote: > https://sourceware.org/bugzilla/show_bug.cgi?id=14641 > > --- Comment #20 from Rich Felker --- > 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 I think all of these examples can be covered with the existing LC_NAME spec. And they were all known at the time of specification. Best regards keld