I see there are a lot of topics on that particular issue, but I recently upgraded to DO13 and I noticed the FTP client wasn't returning filenames in UTF-8.
Did anyone else have that issue?
Auto-detection should work for most sites, but not all, depending on what the server at the other end does.
You can force UTF-8 by editing the site bookmark and turning on Use UTF8 on the Server page.
Hello and thanks for your reply 
I tried that, but alas it still displays filenames without their UTF-8 chars. I don't remember having this issue in DO12.
Is it working with other FTP clients on the same server?
Is there a server we can try connecting to to see the issue?
Yep, I have UTF-8 filenames with Filezilla for example.
@Leo I'm having the exact same issue both over vanilla FTP and SFTP. Special characters showing up as garbage in file listings.
Here is what the log says:
150 Opening ASCII mode data connection for MLSD
UTF8 Error: Invalid <Röyksopp - Melody A.M (2001) [FLAC]>. Reverting to standard char set
211672 bytes received in 0.250 seconds (826.176 Kbytes/sec)
226 Transfer complete
SSH: CTS CONNECTED
SSH: Listing Directory
UTF8 Error: Invalid <Röyksopp - Melody A.M (2001) [FLAC]>. Reverting to standard char set
SSH: List complete 1570 files.
This is with UTF-8 force-enabled on both connections. This is very frustrating since it seems to be a regression with v13. I did not have this issue with DOpus 12 over SFTP.
Server is a boring regular up-to-date Linux machine... nothing exotic whatsoever.
AFAIK this shouldn’t have changed from 12 to 13.
What is the full path to the file that has problems? We can try creating the same thing on a server.
Ok, take this folder name: zakè & anthéne - regeneration (2024) [WEB FLAC 24-44.1]
Here is what it looks like in DOpus 13 when connecting via FTP and with UTF-8 force-enabled
Here is what it looks like in FileZilla over FTP and with UTF-8 force-enabled
I think that what Leo means by full path is from the start (probably something like \\server\path\to\folder).
The full path might be important.
I tried creating a folder with that name on an FTP (not SFTP) site using Filezilla, and then going into it, as well as downloading it, via Opus, and I had no issues.
The "UTF8 Error: Invalid ... Reverting to standard char set" message you're seeing only happens if Opus thinks the string returned by the server is not valid UTF8 data. This may mean it's a server-side issue rather than something Opus is doing wrong. (It could also mean our UTF8 validation code has a mistake, but it works OK when I try on my own FTP server, so the server must be returning something unusual, or it must be something that's part of the rest of the path, not just the folder name.)
I think I understand what's happening. There's a log entry that says something like "invalid character encountered, exiting UTF-8 mode". I checked another app and it's also display garbage in that same place. I think there was an actually invalid character in another folder name in the listing and that was causing the issue. I removed the offending folder and now it's working fine. Thanks.
1 Like