Poor support for unicode file names

Advertisement

jbw
Joined:
Posts:
4
Location:
Poland

Poor support for unicode file names

Recently, I created a converter that transforms ASCII texts into characters from the extended range of UNICODE that resemble letters, and I've been playing with it in various contexts. On Linux (which, like almost all modern systems and applications, operates using UTF-8 encoding) my characters are accepted and displayed correctly. I can name a file using such characters, and everything works and displays properly. Example: ᗯᓰᑎᔑᑕᑭ.Ꭲ᙭Ꭲ. Similarly, in the WinSCP interface, such filenames are displayed correctly, just as they should be. Unfortunately, if we try to rename a file from within the WinSCP interface to one containing UNICODE characters, we end up with a string of question marks ('?').

Reply with quote

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
42,011
Location:
Prague, Czechia

Re: Poor support for unicode file names

What protocol are you using? Does it work with any other client using the same protocol?

Please attach a full session log (on level Debug 2) file showing the problem (using the latest version of WinSCP).

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.

Reply with quote

Advertisement

You can post new topics in this forum