From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Daniel Verite" <daniel@manitou-mail.org>
cc: halilhanbadem@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18196: Databases Created in Turkish Language Will Not Run on
 the Latest Version of Windows
In-reply-to: <48b32b36-1356-43f4-919b-a70dee481304@manitou-mail.org>
References: <48b32b36-1356-43f4-919b-a70dee481304@manitou-mail.org>
Comments: In-reply-to "Daniel Verite" <daniel@manitou-mail.org>
	message dated "Thu, 16 Nov 2023 13:58:24 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <215793.1700143688.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Thu, 16 Nov 2023 09:08:08 -0500
Message-ID: <215794.1700143688@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/215794.1700143688%40sss.pgh.pa.us>
Precedence: bulk

"Daniel Verite" <daniel@manitou-mail.org> writes:
> Aside from the disappearance of the previous name, this "ü" in the new
> name also looks troublesome. It might be encoded as a single byte in
> an encoding of the ISO-8859-* family, in which case the byte would be
> 0xFC it seems, but in an UTF-8 context, it would be represented by the
> sequence 0xC3 0xBC.

Indeed.  That jogged my memory that we've dealt with this sort of
thing before; search the commit log for mentions of "Norwegian (Bokmål)".

I guess we could add mapping entry(s) similar to what we use for that,
although that won't help anybody who's already stuck with an unstartable
database.

			regards, tom lane