5 ms·
You're thinking like a computer programmer who doesn't want to quote or escape their command line arguments. Non-technical users just want to write meaningful
by Simon_says 8y ago
You're thinking like a computer programmer who doesn't want to quote or escape their command line arguments. Non-technical users just want to write meaningful strings and wouldn't understand why a period should be allowed but not a colon. MacOS got this one right. For user-visible names, try to be as permissive as possible and allow as much unicode as possible.
- CamperBob2 8y agoAgree that he's "thinking like a computer programmer" with respect to the distinction between periods and colons, slashes, and so forth. But Unicode is different. If you can't type it on a keyboard, it doesn't belong in a filename.
- Simon_says 8y agoAny person should be able to write filenames in their native language.
- CamperBob2 8y agoNot if they want anyone besides themselves to access the file, they shouldn't. There are some good reasons to allow filenames with Unicode characters, but there are about a zillion good reasons not to.