From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18172 invoked by alias); 17 Oct 2011 01:41:20 -0000 Received: (qmail 18162 invoked by uid 22791); 17 Oct 2011 01:41:19 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,RCVD_IN_DNSWL_LOW,TW_YG X-Spam-Check-By: sourceware.org Received: from out5.smtp.messagingengine.com (HELO out5.smtp.messagingengine.com) (66.111.4.29) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 17 Oct 2011 01:40:53 +0000 Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id E139420BD7 for ; Sun, 16 Oct 2011 21:40:52 -0400 (EDT) Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute4.internal (MEProxy); Sun, 16 Oct 2011 21:40:52 -0400 Received: from [192.168.1.3] (50-88-210-98.res.bhn.net [50.88.210.98]) by mail.messagingengine.com (Postfix) with ESMTPSA id 9A4B4405DEC; Sun, 16 Oct 2011 21:40:52 -0400 (EDT) Message-ID: <4E9B8797.7000200@cwilson.fastmail.fm> Date: Mon, 17 Oct 2011 01:41:00 -0000 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666 MIME-Version: 1.0 To: cygwin-talk@cygwin.com Subject: Re: [ANNOUNCEMENT] Updated: {libiconv/libiconv2/libcharset1}-1.14-2 References: <20111016235917.GB21829@ednor.casa.cgf.cx> In-Reply-To: <20111016235917.GB21829@ednor.casa.cgf.cx> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-talk-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: cygwin-talk-owner@cygwin.com Reply-To: The Vulgar and Unprofessional Cygwin-Talk List Mail-Followup-To: cygwin-talk@cygwin.com X-SW-Source: 2011-q4/txt/msg00013.txt.bz2 On 10/16/2011 7:59 PM, Christopher Faylor wrote: > On Sun, Oct 16, 2011 at 02:20:31PM -0400, Charles Wilson wrote: >> The GNU libiconv package provides an iconv() implementation, for use on >> systems which don't have one, or whose implementation cannot convert >> from/to Unicode. > > Hey, I thought we just had a recent release of iconv. Do we really need > another one so soon?????????????????????? I know you're just being facetious, but actually there truly was no *pressing* need for a libiconv update; we really only needed the gettext/libintl one. However, (a) I usually release both libiconv and gettext together, since they have a circular dependency, and (b) both cygiconv-2.dll and cygcharset-1.dll (from libiconv) shared the same "slow no-op relocation even when --disable-relocation" problem that cygintl-8.dll had. I figured why not fix both... What I'm dreading is one of the following two scenarios: and I fear that if #1 doesn't happen, the odds of #2 occurring approach 98%... #1) I didn't fully fix the original "cygwin started speaking german" problem. I *think* I did, and *my* tests operated as expected, but... #2) Why doesn't cygwin respect my choice of language from Windows Regional Settings? It used to do that, just last WEEK! You finally, after YEARS, fixed cygwin's aberrant behavior -- and then BROKE it again with this latest "update". You guys suck! Yeah, well, WJM. -- Chuck