From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 69303 invoked by alias); 22 Jun 2015 13:21:54 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Received: (qmail 68670 invoked by uid 48); 22 Jun 2015 13:21:48 -0000 From: "myllynen at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug localedata/18408] Provide software utility to permit user created custom locales Date: Mon, 22 Jun 2015 13:21:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: localedata X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: myllynen at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-06/txt/msg00231.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=18408 --- Comment #24 from Marko Myllynen --- (In reply to joseph@codesourcery.com from comment #21) > > localedata is certainly an area that needs someone to become the expert > ... which would include researching common usage in lots of countries / > languages It's easy to agree that there's been certain lack of ownership in this area (I think it's pretty obvious given that even trivial locale patches might take months if not years to get applied) but I'm not sure would such research oriented approach by the glibc community be the best answer here. Since there's already a large and active community working on these issues at Unicode CLDR (including many major vendors of the industry) perhaps we should consider relying on their expertise and using their data where possible (ideally in an automated fashion). If in some cases there would be deviations between glibc and CLDR then we could either update glibc to match CLDR or if the glibc side looks better then report an issue to CLDR. CLDR does not (at least yet) cover everything glibc provides so there would still be some work required by the glibc community but probably far less than trying do everything without CLDR. -- You are receiving this mail because: You are on the CC list for the bug.