3 ms·
Seems like you've had a lot of experience with the products from Sonos. When it comes to file naning, no same system wants to handle colons and other special c
by unixhero 8y ago
Seems like you've had a lot of experience with the products from Sonos.
When it comes to file naning, no same system wants to handle colons and other special characters. I know Macosx and classic has allowed it, and taught users bad manners.
- derriz 8y agoI agree that for shells, some scripting languages and the like, file names with punctuation and other special characters can be challenging. But Sonos doesn't have to do any "handling" here - the user never gets to interact with the network paths/file names so they should (I think) be treated as opaque identifiers.
- Simon_says 8y agoYou'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.