From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20548 invoked by alias); 23 Jun 2014 13:01:53 -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 20440 invoked by uid 89); 23 Jun 2014 13:01:53 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.7 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: Mon, 23 Jun 2014 13:01:00 -0000 From: Keld Simonsen To: fweimer at redhat dot com Cc: libc-locales@sourceware.org Subject: Re: [Bug localedata/14641] Deprecate name_fmt Message-ID: <20140623130123.GA25868@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/msg00196.txt.bz2 On Mon, Jun 23, 2014 at 07:44:34AM +0000, fweimer at redhat dot com wrote: > https://sourceware.org/bugzilla/show_bug.cgi?id=14641 > > --- Comment #24 from Florian Weimer --- > (In reply to keld@keldix.com from comment #21) > > 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. > > I think the discrimination of married vs unmarried women in name formatting is > now considered obsolete and perhaps even slightly offensive. Then you can make them the same (Ms). > In any case, proper name formatting is not something related very strongly to > culture anymore, but to individual persons and the relationships among them. > Locales are more or less country-based, so they are a poor way to select name > formatting rules. The locales are culturally oriented. I cannot speak for every culture, but proper name formatting still seems relevant in many cultures. What we have is not perfect, but it can be used to provide more culturally acceptable results. But I think there is room for improvement, I invite such suggestions for improvement. Do you have any suggestions? > Even telephone number formatting isn't as straightforward as it may seem. In > Germany, there are three major ways of formatting phone numbers, and it seems > that de_DE.UTF-8 uses neither of them (it's difficult to tell because the > formatting codes are undocumented). The idea was at least to get rid of the USA way, which is not culturally acceptable in many countries. Then a number of ways would be kind of OK - in my country there are also some common examples, and then there is an official recommendation. Best regards keld