From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: cygwin-talk@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: {libiconv/libiconv2/libcharset1}-1.14-2
Date: Mon, 17 Oct 2011 01:41:00 -0000 [thread overview]
Message-ID: <4E9B8797.7000200@cwilson.fastmail.fm> (raw)
In-Reply-To: <20111016235917.GB21829@ednor.casa.cgf.cx>
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
next prev parent reply other threads:[~2011-10-17 1:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <announce.20111016182240.039CE4833D9@frontend2.nyi.mail.srv.osa>
2011-10-16 23:59 ` Christopher Faylor
2011-10-17 1:41 ` Charles Wilson [this message]
2011-10-17 12:55 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E9B8797.7000200@cwilson.fastmail.fm \
--to=cygwin@cwilson.fastmail.fm \
--cc=cygwin-talk@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).