From: Tom Lane <tgl@sss.pgh.pa.us>
To: oystein.arneson@cloudberries.no
cc: pgsql-bugs@lists.postgresql.org
Subject: =?UTF-8?Q?Re:_BUG_#18795:_Norwegian_bokm=C3=A5l_crashes_again?=
In-reply-to: <18795-268389c4e50cbd4e@postgresql.org>
References: <18795-268389c4e50cbd4e@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Wed, 05 Feb 2025 07:38:47 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <816215.1738772073.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 05 Feb 2025 11:14:33 -0500
Message-ID: <816216.1738772073@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/816216.1738772073%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> I downloaded the latest installer for windows and tried to install a loc=
al
> database server with locale Norwegian Bokm=C3=A5l. Looks like this bug i=
s back in
> version 17? Or maybe it's windows 11 that is causing it? =


Sigh, did they rename it again?  Our last commit log entry about
this explains

    It emerges that recent versions of Windows (at least 2016 Standard)
    spell this locale name as "Norwegian Bokm=C3=A5l_Norway.1252", defeati=
ng
    our mapping code that translates "Norwegian (Bokm=C3=A5l)_Norway" to
    something that's all-ASCII (cf commits db29620d4 and aa1d2fc5e).
    Add another mapping entry to handle this spelling.

Can you identify how it's spelled in W11?  Also, what failure
are you seeing *exactly*?

			regards, tom lane