Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows

From: Koichi Suzuki <koichi(dot)dbms(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Tatsuo Ishii <ishii(at)postgresql(dot)org>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
Date: 2024-12-06 06:11:49
Message-ID: CABEZHFsmies3X5BJ5xGZVrOeMikwwR7GVGhQ9N4Ee7OsKXi3OQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

In the Japanese version of Windows, file names are in Shift-JIS.

For sure, we need to check client_encoding.

Regards;
---
Koichi Suzuki
https://www.linkedin.com/in/koichidbms

2024年12月6日(金) 14:44 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:

> Tatsuo Ishii <ishii(at)postgresql(dot)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
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Koichi Suzuki 2024-12-06 06:13:30 Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
Previous Message Tom Lane 2024-12-06 05:54:15 Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows