syncthing: File name ... contains invalid characters; marked as invalid.
10:02:47: File name "BSC-Share/Einmal neuer Server, bitte. Mit viel Salz… | 21x9.org.webloc" contains invalid characters; marked as invalid.
10:02:47: File name "BSC-Share/Bett/Polsterbett Catana dunkelbraun | massivum.de.webloc" contains invalid characters; marked as invalid.
10:02:47: File name "Bett/Betten, Polsterbett \"Seaside Richmond\" - Clever & Günstig kaufen.webloc" contains invalid characters; marked as invalid.
10:02:47: File name "BSC-Share/naeramarth7:clean-greader · GitHub.webloc" contains invalid characters; marked as invalid.
10:02:47: File name "BSC-Share/Onkyo | A-5VL.webloc" contains invalid characters; marked as invalid.
Filenames:
Einmal neuer Server, bitte. Mit viel Salz… | 21x9.org.webloc
Polsterbett Catana dunkelbraun | massivum.de.webloc
Betten, Polsterbett "Seaside Richmond" - Clever & Günstig kaufen.webloc
naeramarth7/clean-greader · GitHub.webloc
Onkyo | A-5VL.webloc
They are also deleted on other nodes but still on that node.
About this issue
- Original URL
- State: closed
- Created 10 years ago
- Comments: 18 (10 by maintainers)
I feel like files should still be copied, albeit with invalid characters encoded in a manner that the target filesystem supports. Since Windows and NTFS is likely the target to complain the most, maybe the filenames could have their invalid characters URL encoded; like
%2Afor*,%3Afor:and others? The target syncthing instance wouldn’t need to keep a table mapping, it would just decode the parts back to the correct character.