From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tatsuo Ishii <ishii@postgresql.org>
cc: koichi.dbms@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18735: Specific multibyte character in psql file path
 command parameter for Windows
In-reply-to: <20241206.142130.1661155698933375612.ishii@postgresql.org>
References: <18735-4acdb3998bb9f2b1@postgresql.org>
 <2572359.1733424649@sss.pgh.pa.us>
 <20241206.142130.1661155698933375612.ishii@postgresql.org>
Comments: In-reply-to Tatsuo Ishii <ishii@postgresql.org>
	message dated "Fri, 06 Dec 2024 14:21:30 +0900"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2750621.1733463850.1@sss.pgh.pa.us>
Date: Fri, 06 Dec 2024 00:44:10 -0500
Message-ID: <2750622.1733463850@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2750622.1733463850%40sss.pgh.pa.us>
Precedence: bulk

Tatsuo Ishii <ishii@postgresql.org> writes:
>> This might mean that it'd be okay to just skip the backslash-to-slash
>> conversion loops altogether if we think the encoding is Shift-JIS.

> I suggest to not do so because majority of Shift-JIS users treat 0x5C
> as a backslash. They understand that a 0x5C means a backslash in
> Shift-JIS files if the files are for programming (source code) or for
> the technical documentations and so on.

Sure, we can do it that way.  I think the hard part is figuring
out whether Windows thinks the file names are in Shift-JIS.
Do you have any idea about finding that out?

			regards, tom lane