Since this is my first post here, first things first, let me tell you how much I love FFS! Amazing piece of software!
Now to the feature request: Linux <=> Windows filename colon support
FFS version: 11.18 64bit
When syncing files between Linux and Windows filesystems, files that have a colon (:) in their name on Linux are not considered to be the same as their percent-encoded (%3A) counterpart on Windows:
Taking it one step further, copying those files from Linux to Windows causes the following error:
But copying these files from Windows to Linux results in files being copied in their percent-encoded form.
I'm not sure how that's supposed to work but another piece of software I use, WinSCP, does
: => %3A encoding when copying from Linux to Windows
%3A => : decoding when copying from Windows to Linux
Also found this behavior documented here:
https://www.ibm.com/docs/en/spectrum-archive-sde/2.4.1.0?topic=tips-file-name-characters
> On Windows systems, files and directory names cannot be created with a colon (:). But if a file or directory name is created with a colon on a Linux or Mac operating system, then moved to a Windows system, percent encoding is used to include the colon in the name in the index.
Linux <=> Windows filename colon support
- Posts: 2
- Joined: 9 Apr 2022
You do not have the required permissions to view the files attached to this post.
- Posts: 4949
- Joined: 11 Jun 2019
- Posts: 2
- Joined: 9 Apr 2022
Thanks for the links! I totally agree that this is the fault of a user/dev who decides to create a file with "shady" characters that don't play well across multiple filesystems. That's why I'm calling it a feature request, not a bug report. Far from a dealbreaker for me but for someone it might be so just wanted to leave my two cents here.