Re: setlocale() issue on Windows with UTF-8

[Bruno Haible]

Hi Lasse,

Lasse Collin wrote:
> I haven't learned yet how to produce a distribution tarball from
> gettext.git but I didn't try for many minutes either. I ran autogen.sh
> successfully etc. but, for some some reason I don't understand, "make
> dist" wants to build the package first and then it fails because I
> didn't install ppcx64.

The INSTALL file refers to the HACKING file for this situation, and the
HACKING file has the (long) list of prerequisites.

But there's a shortcut:
  - You can download a snapshot tarball from the
    GitLab CI, if you have a GitLab account. Today the link is
    https://gitlab.com/gnu-gettext/ci-distcheck/-/jobs/8714519943
    click "Download", and in the downloaded artifacts there is a
    gettext-snapshot.tar.
  - Similarly there is a snapshot tarball at the GitHub CI. Today
    the link is
    https://github.com/gnu-gettext/ci-check/actions/runs/12493509240
    click on "tarball".

> Instead, I started with 0.22.5 tarball (I know, not the latest
> release). I copied newer Gnulib files to intl/gnulib-lib and newer
> Gettext setlocale.c to to intl. And indeed, it seems to work now. :-)

That is more work. Glad it worked out!

> This might not matter but I mention it just in case. Your sample
> outputs *before* the fix were different than I expected:
> 
>   - I got "fi_FI" with unmodified gettext 0.22.5 when not in UTF-8
>     mode. "en_US" would be fine too. I don't understand how the old
>     gettext could produce "C" on native Windows.

Different Windows installations sometimes operate differently.
I wouldn't be surprised if the difference is hidden in the registry...

Bruno