| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Cc: | koichi(dot)dbms(at)gmail(dot)com, 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 05:44:10 |
| Message-ID: | 2750622.1733463850@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-12-06 05:54:15 | Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows |
| Previous Message | Koichi Suzuki | 2024-12-06 05:26:34 | Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows |