From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
cc: egashira.yusuke@fujitsu.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17611: SJIS conversion rule about duplicated characters
 differ from Windows
In-reply-to: <20220909.114216.2263659117945873025.horikyota.ntt@gmail.com>
References: <17611-472d27cf395135b7@postgresql.org>
 <20220909.114216.2263659117945873025.horikyota.ntt@gmail.com>
Comments: In-reply-to Kyotaro Horiguchi <horikyota.ntt@gmail.com>
	message dated "Fri, 09 Sep 2022 11:42:16 +0900"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <5963.1662692311.1@sss.pgh.pa.us>
Date: Thu, 08 Sep 2022 22:58:31 -0400
Message-ID: <5964.1662692311@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/5964.1662692311%40sss.pgh.pa.us>
Precedence: bulk

Kyotaro Horiguchi <horikyota.ntt@gmail.com> writes:
> This is not a bug, but the designed behavior. But we could change that
> conversion table if a plausible reasoning is raised.

Given how long our current behavior has stood, I think it'd have to be
a pretty convincing argument.  As you say, there'd be some serious
compatibility costs to changing that behavior.

IIUC, SJIS<->Unicode conversions have always been a squishy thing
because of inconsistencies between the various versions of "SJIS".
I'm not seeing a good reason we should regard Windows' behavior as
authoritative here.

I'm not saying I can't be convinced, but "Microsoft does it that
way" isn't enough to convince me.

			regards, tom lane