* Re: [ANNOUNCEMENT] Updated: {libiconv/libiconv2/libcharset1}-1.14-2
[not found] <announce.20111016182240.039CE4833D9@frontend2.nyi.mail.srv.osa>
@ 2011-10-16 23:59 ` Christopher Faylor
2011-10-17 1:41 ` Charles Wilson
0 siblings, 1 reply; 3+ messages in thread
From: Christopher Faylor @ 2011-10-16 23:59 UTC (permalink / raw)
To: cygwin-talk
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??????????????????????
cgf
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [ANNOUNCEMENT] Updated: {libiconv/libiconv2/libcharset1}-1.14-2
2011-10-16 23:59 ` [ANNOUNCEMENT] Updated: {libiconv/libiconv2/libcharset1}-1.14-2 Christopher Faylor
@ 2011-10-17 1:41 ` Charles Wilson
2011-10-17 12:55 ` Christopher Faylor
0 siblings, 1 reply; 3+ messages in thread
From: Charles Wilson @ 2011-10-17 1:41 UTC (permalink / raw)
To: cygwin-talk
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [ANNOUNCEMENT] Updated: {libiconv/libiconv2/libcharset1}-1.14-2
2011-10-17 1:41 ` Charles Wilson
@ 2011-10-17 12:55 ` Christopher Faylor
0 siblings, 0 replies; 3+ messages in thread
From: Christopher Faylor @ 2011-10-17 12:55 UTC (permalink / raw)
To: cygwin-talk
On Sun, Oct 16, 2011 at 09:40:39PM -0400, Charles Wilson wrote:
>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.
I stand inexplicably corrected.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-10-17 12:55 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <announce.20111016182240.039CE4833D9@frontend2.nyi.mail.srv.osa>
2011-10-16 23:59 ` [ANNOUNCEMENT] Updated: {libiconv/libiconv2/libcharset1}-1.14-2 Christopher Faylor
2011-10-17 1:41 ` Charles Wilson
2011-10-17 12:55 ` Christopher Faylor
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).