cygwin started speaking German today

Erwin Waterlander
Tue Oct 11 15:41:00 GMT 2011

On 10/10/2011 7:23 PM, Corinna Vinschen wrote:
> Chuck, ping?
> On Oct  5 14:23, Ken Brown wrote:
>> On 10/5/2011 1:31 PM, Charles Wilson wrote:
>>> On 10/5/2011 12:27 PM, Corinna Vinschen wrote:
>>>> On Oct  5 18:04, Erwin Waterlander wrote:
>>>>> Op 4-10-2011 20:20, Corinna Vinschen schreef:
>>>>>> On Oct  4 20:03, Erwin Waterlander wrote:
>>>>>>> By the way, I noticed that with the default locale C.UTF-8 the
>>>>>>> nl_langinfo(CODESET) C function<langinfo.h>    returns wrongly
>>>>>>> "ISO-8859-1",
>>>>>> Not for me:
>>>>>> [...]
>>>>> My program (wcd) uses gettext/libintl. Libintl is causing the
>>>>> effect. Libintl is not working properly with a locale C.UTF-8. That
>>>>> is a serious problem.
>>>> That's a bug in libintl8  It does not happen with the
>>>> previous version 0.17-11.  Hopefully this gets fixed ASAP.
>> [...]
>>> The other is the issue that spawned this thread, which raised questions
>>> about how basefiles::/etc/profile.d/lang.{sh,csh} should behave, and
>>> other related complexities.  IIRC we reached an impasse with this
>>> subthread (and replies):
>>> See also the various messages in this thread, during the last day or two.
>>> So...I'm rather stuck.  I can't fix anything if we don't have a plan for
>>> what the desired behavior IS.  Right now, we all (except for Bruno!)
>>> agree that $current_behavior is bad.  But how exactly to fix it -- and
>>> whether to do so in opposition to Bruno, the actual libintl maintainer
>>> -- is still an open question.
>> I think you're mixing two questions that should be kept separate.
>> The first is how /etc/profile.d/lang.{sh,csh} should set LANG.
>> That's a question that the Cygwin developers and/or base-files
>> maintainer need to decide.  The second is whether libintl should
>> override Cygwin's locale settings.  Isn't the answer clearly no?
>> Why can't this be fixed (in opposition to Bruno, if necessary)
>> before a final decision is made about /etc/profile.d/lang.{sh,csh}?
>> I don't recall any complaints from Cygwin users about C.UTF-8 being
>> the default, but there have already been several complaints about
>> the new behavior of libintl.
> This is *really* annoying behaviour.  Right now the gawk testsuite
> fails, because libintl thinks it has to use the german language,
> even though $LANG is set to C.UTF-8.
> What's even more annoying is the fact that it's not sufficient to revert
> libintl8 to 0.17-11, but you also have to revert gettext-devel to
> 0.17-11 *and* recompile gawk, because the 0.18.1 version redefines
> setlocale to libintl_setlocale.  The effect is that applications built
> against 0.18 don't run with the 0.17 DLL.  Thus, if you don't have
> control over the binary (aka "normal Cygwin user"), you can not even
> revert to libintl8 0.17-11, because that may break newly built
> applications.
> Please consider to provide a new libintl/gettext without this bug soon.

Indeed! My application doesn't work correctly, because the wrong 
character encoding is returned. I get ISO-8859-1 while I should get 
UTF-8. And while bypassing Cygwin's locale it doesn't even do that 
properly. Libintl returns ISO-8859-1 while my Windows' locale character 
encoding is CP1252 (which isn't the same).


Problem reports:
Unsubscribe info:

More information about the Cygwin mailing list