From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 37558 invoked by alias); 30 Jun 2015 13:54:19 -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 37048 invoked by uid 48); 30 Jun 2015 13:53:44 -0000 From: "carlos at redhat dot com" To: libc-locales@sourceware.org Subject: [Bug localedata/18568] Update locale data to Unicode 8.0 Date: Tue, 30 Jun 2015 13:54: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: 2.21 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: carlos 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: 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-q2/txt/msg00122.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=18568 --- Comment #13 from Carlos O'Donell --- (In reply to Paul Wise from comment #12) > On Mon, Jun 29, 2015 at 08:04:58PM +0000, carlos at redhat dot com wrote: > > > Stability. We want to test and validate one version of Unicode > > data and update the implementation to match. > > Is that testing and validation automated or manual? In the past the testing and validation was entirely manual, which is why automatically migrating to a new version of Unicode was difficult and potentially error prone. With the recent update by the Fedora i18n team (Mike Fabian, Pravin Satpute) and with help of Alexandre Oliva (Red Hat), we were able to automate the update of the character encoding and ctype tables. This update included regression testing scripts that verify backwards compatibility automatically. So in some ways we have automatic testing for that component of the locales, but given the broader changes in Unicode 8.0, someone should do the work and verify the results. If you want to try update to Unicode 8.0, you can do so by looking at localedata/unicode-gen/Makefile, updating the external properties files, and running `make all` in that unicode-gen directory (distinct from glibc build). -- You are receiving this mail because: You are on the CC list for the bug.