From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6658 invoked by alias); 23 May 2014 12:02:45 -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 6309 invoked by uid 55); 23 May 2014 12:02:40 -0000 From: "joseph at codesourcery dot com" To: glibc-bugs@sourceware.org Subject: [Bug localedata/14094] Update locale data to Unicode 6.3 Date: Fri, 23 May 2014 12:02: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.15 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: joseph at codesourcery dot com X-Bugzilla-Status: NEW 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: 2014-05/txt/msg00163.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=14094 --- Comment #4 from joseph at codesourcery dot com --- Once the data is updated (maybe once just the character map is updated), __STDC_ISO_10646__ should be updated in include/stdc-predef.h to reflect the publication date of the edition or amendment to ISO 10646 corresponding to the version of Unicode in use. I advise keeping each of the tasks I listed as a separate patch, as it's important to be confident we aren't losing desired local changes in the course of the update (which means the existing files need to be reproduced exactly by some automation before the update is done). Bug 16061 relates to transliteration data, some of which came from Unicode, and bug 14095 to collation data. The same principles apply to those - reproduce the existing files, understanding any local changes in the process, then update to a newer Unicode version - but they are likely to involve much more work in understanding the existing state then updating while preserving any desired local changes. -- You are receiving this mail because: You are on the CC list for the bug.