Editing folder names that would end in a regular ASCII period character (".")

[etui-null]

Hey everyone, I recently noticed a weird thing happening in an archive I have on a Synology NAS (a linux environment), I noticed some folder names were being renamed into a weird format that looked something like H6J0D9~R. Turns out this is a limitation in Windows path names when using NTFS that does not allow the ASCII period character (".") to be appended to file or directory properly. Obviously, this isn't an issue when not using NTFS, but as I also view these files occasionally on a Windows machine I was hoping someone could point me towards a way to edit my config to replace only any trailing periods with a replacement character. I've been using ． which is the unicode fullwidth full stop (U+FF0E) as that's what a different archival program I use edits filenames with. Ideally, I would like to keep any ASCII periods that show up elsewhere in the filename, so I was hoping to avoid a blanket replacement (e.g. using the path-restrict config option).

[mikf]

Set path-strip to "windows" or directly to ". ".

[etui-null]

Oh that literally addresses this exact issue. Perfect lol, thank you!

[etui-null]

I just reran a few tests with path-strip set, worked great, but I think I'm a little confused as to why there's a space present in ". "
Could you explain what purpose the space has here?

[mikf]

It removes both periods . as well as spaces .

Spaces are also not allowed at the end of filesystem names.

Do not end a file or directory name with a space or a period. Although the underlying file system may support such names, the Windows shell and user interface does not. However, it is acceptable to specify a period as the first character of a name. For example, ".temp".

(https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file#naming-conventions)

[etui-null]

Okay that's what I assumed, had read that same article, just wanted to double check. Thanks again!