From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 607 invoked by alias); 13 Aug 2006 10:24:02 -0000 Received: (qmail 572 invoked by uid 48); 13 Aug 2006 10:23:54 -0000 Date: Sun, 13 Aug 2006 10:24:00 -0000 Message-ID: <20060813102354.571.qmail@sourceware.org> From: "leonard-glibc-bugs at ottolander dot nl" To: glibc-bugs@sources.redhat.com In-Reply-To: <20060619132408.2798.leonard-glibc-bugs@ottolander.nl> References: <20060619132408.2798.leonard-glibc-bugs@ottolander.nl> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug libc/2798] localedata/locales % Charset comment string fixes X-Bugzilla-Reason: CC Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org X-SW-Source: 2006-08/txt/msg00102.txt.bz2 List-Id: ------- Additional Comments From leonard-glibc-bugs at ottolander dot nl 2006-08-13 10:23 ------- I don't mind fixing this patch, but I'm unsure as to which hunks would be allowable and which aren't. F.e. is -% Charset: CP1251 +% Charset: CP1251, UTF-8 for be_BY acceptable? (UTF-8 being in use for this locale) How about -% Charset: BALTIC +% Charset: ISO-8859-13 for lt_LT? I would say "no" according to your remark, but what charset is "BALTIC"? How about the addition +% Charset: UTF-8 for bg_BG which doesn't have a charset mentioned in the comments yet? Maybe it's just easiest if you handpick acceptable hunks yourself. That should be much less work than having to go back and forth a couple of times. -- What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |NEW http://sourceware.org/bugzilla/show_bug.cgi?id=2798 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.