Comment by kalleboo
10 hours ago
macOS can also handle files with any of those characters in the filename, it's only Windows that's affected.
10 hours ago
macOS can also handle files with any of those characters in the filename, it's only Windows that's affected.
Not colon.
It can handle files with colon in the name fine, Finder just won't let you name them like that. The files themselves work fine if you created them in the Terminal/through sync.
Classic MacOS used colon as a path separator, so to support creating files that could be opened on classic MacOS the Finder disallows it.
You mean 90% of desktop users…
I am surprised that the # symbol isn’t on the list.