Issues with special characters in filenames

[markv]

I am running BC4 on a Windows 8 desktop and have an issue with file name compares.
If the filename has a special character e.g. ü it works fine when comparing two windows directories. However when comparing the windows directory to a directory on a FTP host, it shows a � symbol (on the FTP side). See the attached screenshot. Files are then considered to have a different name.

This issue does not occur when running BC version 3.

Mark

[Aaron]

Hello,

Would it be possible to get an FTP debug log showing the file listing of this directory/comparison?

To enable debug logging, go to the Tools menu -> Options, Tweaks section, and scroll down to the Log Panel section. Enable all of the options here, including Debug Messages. Then connect to the server, and then save the bottom green log pane.

You can then post or, assuming private information, email us at [email protected]. If you email, please include a link back to this forum thread for our reference.

[markv]

Sent the FTP log file to the support mail address.

[GeorgAdamsen]

Hello,

Would it be possible to get an FTP debug log showing the file listing of this directory/comparison?

To enable debug logging, go to the Tools menu -> Options, Tweaks section, and scroll down to the Log Panel section. Enable all of the options here, including Debug Messages. Then connect to the server, and then save the bottom green log pane.

You can then post or, assuming private information, email us at [email protected]. If you email, please include a link back to this forum thread for our reference.

Hi,

I see the same problem. BCompare 4 displays ut-f8 filenames erroneously while CuteFTP recognises the utf-8 filenames returned by the server software (SFTPBlackbox 5.0) correctly. Do you need more logs and sceendumps?

By the way, I would not label Danish characters as special characters in a modern file system environment! :-)

Best regards,

Georg

[markv]

For clarity it would be better to move this post to the "Beyond Compare 4 Discussion" forum

[Aaron]

Hello,

If you change the FTP Profile from auto-detect to either UTF-8 or ANSI, then restart BC4 and reconnect to the FTP, which of these two encodings works to display your file names correctly.


BC4 did have a change in behavior over BC3 in a specific scenario:
If the server software previously didn't report as UTF8, we would default to upload as ANSI. The server can later be updated and will then report itself as UTF8. For BC3, it would see this, but then scan and *potentially* still use ANSI since it finds ANSI files. This results in things displaying "correctly", but actually in the incorrect encoding for the server, and would continue to upload as ANSI as well.
BC4 changed this, and when it sees UTF8 it will begin using UTF8. This results in current/future files uploading and displaying correctly, but previously uploaded files will need to be renamed or re-uploaded to use the new UTF8 standard.

[markv]

That worked for me.
I changed the FTP profiles to ANSI and uploaded the problem files again.
Now they show up correct.

Thanks.

[Aaron]

If your server is now detecting as UTF8, it might help to change to UTF8 and then try reuploading once more. This would result in the previously uploaded files having the problem until they are reuploaded, but it would technically follow what the server expects going forward. Just be sure to restart Beyond Compare after changing the option; just to be sure it's applied.