Date: Fri, 06 Dec 2024 15:29:01 +0900 (JST)
Message-Id: <20241206.152901.833675745256351050.ishii@postgresql.org>
To: tgl@sss.pgh.pa.us
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
From: Tatsuo Ishii <ishii@postgresql.org>
In-Reply-To: <2750622.1733463850@sss.pgh.pa.us>
References: <2572359.1733424649@sss.pgh.pa.us>
	<20241206.142130.1661155698933375612.ishii@postgresql.org>
	<2750622.1733463850@sss.pgh.pa.us>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/20241206.152901.833675745256351050.ishii%40postgresql.org>
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?

I am not familiar with Windows and have no idea, but from the original
report:

postgres=# \cd 'c:/work/09_環境構築'

it seems the KANJI characters are shown properly even if a part of the
KANJI characters include a backslash. This could indicate Windows
thinks the file names are in Shift-JIS.

Best reagards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp