Re: supporting in the UTF-8 environment on native Windows

I commented on bug-gettext that these fixes work for me when environment variables LANG, LC_*, or LANGUAGE aren't set. Thanks again! The commit 00211fc69c92 ("setlocale: Support the UTF-8 environment on native Windows.") introduces Windows support for C.UTF-8 in setlocale.c. Emulating C.UTF-8 with

Re: supporting in the UTF-8 environment on native Windows

Lasse Collin wrote: > Thanks. Isn't there a similar issue in setlocale.c after the commit > 00211fc69c92? > > /* llCC_buf now contains >language[_territory][@modifier] >*/ > if (strcmp (llCC_buf, locale) != 0) > { > if (is_utf8) > { >

Re: supporting in the UTF-8 environment on native Windows

On 2024-12-24 Bruno Haible wrote: > Lasse Collin wrote: > > (1) > > In 9f7ff4f423cd ("localename-unsafe: Support the UTF-8 environment > > on native Windows."), the N(name) macro is used with strings that > > include @modifier. For example, N("az_AZ@cyrillic") can expand to > > "az...@cyrillic.utf-

Re: supporting in the UTF-8 environment on native Windows

Lasse Collin wrote: > (1) > In 9f7ff4f423cd ("localename-unsafe: Support the UTF-8 environment on > native Windows."), the N(name) macro is used with strings that include > @modifier. For example, N("az_AZ@cyrillic") can expand to > "az...@cyrillic.utf-8". Similarly in 00211fc69c92 ("setlocale: Sup

Re: supporting in the UTF-8 environment on native Windows

On 2024-12-23 Bruno Haible wrote: > Lasse Collin reported in > > that the setlocale() override from GNU libintl does not support the > UTF-8 environment of native Windows correctly. That setlocale() > override is based on the se

supporting in the UTF-8 environment on native Windows

Lasse Collin reported in that the setlocale() override from GNU libintl does not support the UTF-8 environment of native Windows correctly. That setlocale() override is based on the setlocale() override from gnulib. So let me ad