This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: 1.7.7: Localization does not follow the language of the OS

Replying to <>:

>> I think that doing setlocale(LC_ALL, ""); on application initialization
>> should do the trick.
> Yes it does - assuming you use a libintl from gettext version >= 0.18,
> and assuming that you have a #include <libintl.h> in the source file that
> invokes setlocale (LC_ALL, "").
> This was implemented in gettext 0.18.

I have a #include <libintl.h> in the source file that invokes setlocale.
Now that I look at it again: actually I'm doing setlocale(LC_MESSAGES, "")
instead of setlocale(LC_ALL, ""), because I only want translation of the
message texts. I suppose it shouldn't matter for this discussion, but I
mention it anyway, just in case it does matter.

I also happen to supply an 'intl' directory with my application, which
contains a gettext implementation. It can be activated by giving the
--with-included-gettext parameter to the configure script of my
application. I tried whether this would fix my problem, but it doesn't;
I guess because my included gettext is also version 0.17.

Would it help to update my included gettext to version 0.18? Or would this
just give me compilation headaches on Cygwin? I noticed that setlocale is
not implemented in my included gettext, so I suppose that setlocale has to
be supplied by Cygwin anyway. Does this mean that it will never make a
difference for me to use the included gettext, or is it possible to somehow
influence the behavior of setlocale with the included gettext version?

Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]