Follow-up Comment #2, bug #43801 (project gettext):
I don't think this patch is correct. The application could change the locale
by calling SetThreadLocale (or any equivalent call, like the global
setlocale), and after that it should get the translations according to that
locale's language. If we use GetUserDefaultUILanguage, there will be no way
for the application to affect the current language and codeset through
locale-related calls. This is important in applications that change locales
for various reasons (e.g., Guile does that).
So if we need to change here something, we will need a better understanding of
the situation you had in mind. Could you please describe the problem in more
detail? Exactly when would the locale's language and the language returned by
GetUserDefaultUILanguage be in conflict, and how can this conflict come into
existence?
Thanks.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?43801>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
