Hello,
when trying to fetch a directory with a file with an invalid charset from an ftp server the whole directory is skiped. Is it possible to skip just the one file?
FTP: Filenames in wrong char set
- Posts: 31
- Joined: 17 Jul 2019
- Attachments
-
- ffs.png (7.28 KiB) Viewed 816 times
- Posts: 31
- Joined: 17 Jul 2019
After changing the file name, I got another error message on another file:
-----------
Die Datei "ftp://thomas@192.168.188.76/home/thomas/Downloads/FA Einzugsermächtigung 2023.pdf" kann nicht gelesen werden.<br>
Die Zeichenkodierung konnte nicht automatisch erkannt werden: /home/thomas/Downloads/FA Einzugsermächtigung 2023.pdf
---
Translation: The character encoding could not be detected automatically
-----------
Die Datei "ftp://thomas@192.168.188.76/home/thomas/Downloads/FA Einzugsermächtigung 2023.pdf" kann nicht gelesen werden.<br>
Die Zeichenkodierung konnte nicht automatisch erkannt werden: /home/thomas/Downloads/FA Einzugsermächtigung 2023.pdf
---
Translation: The character encoding could not be detected automatically
- Site Admin
- Posts: 7211
- Joined: 9 Dec 2007
The server doesn't advertize itself as being UTF8-compatible, apparently.
When you run the "FEAT" command on the FTP server, what does it return?
When you run the "FEAT" command on the FTP server, what does it return?
- Posts: 31
- Joined: 17 Jul 2019
I have changed the server settings, but there is still a problem:
<td>Das Verzeichnis "ftp://thomas@192.168.188.76/home/thomas/Downloads" kann nicht gelesen werden.<br>
Unexpected FTP response. (-rw-r--r-- 1 1000 1000 185608 Jan 28 13:27 FA Einzugserm�chtigung 2023.pdf) Ungültige Zeichenkodierung: [UTF-8] FA Einzugserm�chtigung 2023.pdf</td>
--------------------------
C:\Users\benne>ftp 192.168.188.76
Verbindung mit 192.168.188.76 wurde hergestellt.
220 (vsFTPd 3.0.3)
200 Always in UTF8 mode.
Benutzer (192.168.188.76:(none)): thomas
331 Please specify the password.
Kennwort:
230 Login successful.
ftp> FEAT
Ungültiger Befehl
ftp> FEAT
Ungültiger Befehl
ftp>
------
<td>Das Verzeichnis "ftp://thomas@192.168.188.76/home/thomas/Downloads" kann nicht gelesen werden.<br>
Unexpected FTP response. (-rw-r--r-- 1 1000 1000 185608 Jan 28 13:27 FA Einzugserm�chtigung 2023.pdf) Ungültige Zeichenkodierung: [UTF-8] FA Einzugserm�chtigung 2023.pdf</td>
--------------------------
C:\Users\benne>ftp 192.168.188.76
Verbindung mit 192.168.188.76 wurde hergestellt.
220 (vsFTPd 3.0.3)
200 Always in UTF8 mode.
Benutzer (192.168.188.76:(none)): thomas
331 Please specify the password.
Kennwort:
230 Login successful.
ftp> FEAT
Ungültiger Befehl
ftp> FEAT
Ungültiger Befehl
ftp>
------
- Site Admin
- Posts: 7211
- Joined: 9 Dec 2007
I think the syntax for the "ftp" tool is
literal FEAT
- Posts: 31
- Joined: 17 Jul 2019
ftp> literal FEAT
211-Features:
UTF8
EPRT
EPSV
MDTM
PASV
REST STREAM
SIZE
TVFS
211 End
ftp>
211-Features:
UTF8
EPRT
EPSV
MDTM
PASV
REST STREAM
SIZE
TVFS
211 End
ftp>
- Site Admin
- Posts: 7211
- Joined: 9 Dec 2007
Apparently the servers does support UTF8.
Which settings did you change?I have changed the server settings
- Posts: 31
- Joined: 17 Jul 2019
I have enabled the UTF-8 support in the config file but get still this error:
<td>Das Verzeichnis "ftp://thomas@192.168.188.76/home/thomas/Downloads" kann nicht gelesen werden.<br>
Unexpected FTP response. (-rw-r--r-- 1 1000 1000 185608 Jan 28 13:27 FA Einzugserm�chtigung 2023.pdf) Ungültige Zeichenkodierung: [UTF-8] FA Einzugserm�chtigung 2023.pdf</td>
<td>Das Verzeichnis "ftp://thomas@192.168.188.76/home/thomas/Downloads" kann nicht gelesen werden.<br>
Unexpected FTP response. (-rw-r--r-- 1 1000 1000 185608 Jan 28 13:27 FA Einzugserm�chtigung 2023.pdf) Ungültige Zeichenkodierung: [UTF-8] FA Einzugserm�chtigung 2023.pdf</td>
- Site Admin
- Posts: 7211
- Joined: 9 Dec 2007
The � character is an ANSI-encoded "ä" stored on the server, decoded as UTF8 by the client (FFS). In other words it's corrupted data from FreeFileSync's perspective. The simplest fix would be to delete the file and upload again. This time it will be correctly UTF8-encoded.
- Posts: 31
- Joined: 17 Jul 2019
Is it possible to switch it to ANSI instead? Whenever a file is saved on the debian homeserver, the filename seems to be Ansi encoded.
- Site Admin
- Posts: 7211
- Joined: 9 Dec 2007
This issue has been fixed for the next release:Die Zeichenkodierung konnte nicht automatisch erkannt werden: /home/thomas/Downloads/FA Einzugsermächtigung 2023.pdf
---
Translation: The character encoding could not be detected automatically thbenner, 26 Feb 2023, 10:15
https://www.mediafire.com/file/sir094feluq2t4t/FreeFileSync_12.2_%255BBeta%255D_Windows_Setup%25282%2529.exe
This seems to be a bug of the FTP app that saved this file. Apparently the connection was UTF8, but the app sent the file name as ANSI instead.Is it possible to switch it to ANSI instead? Whenever a file is saved on the debian homeserver, the filename seems to be Ansi encoded. thbenner, 26 Feb 2023, 15:05
- Posts: 31
- Joined: 17 Jul 2019
Thank you very much!