open https://gitlab.synchro.net/main/sbbs/-/issues/753

ISO-9660 (file system for CD-ROMs) limits filenames to uppercase letters, digits, dot, and underscore. No dash (-) or lowercase letters. This could be another restriction for uploaded filenames, if a sysop was planning to archive the files to ISO-9660 storage.

This would be a more restricted character set than the "Safest subset" and likely cause rejection of a lot of uploaded files, so then we might want to have uploaded filenames auto-converted (upper-cased, dashes converted to underscores). Maybe nobody really needs this. Just an idea, now that I realize how restrictive ISO-9660 really is.
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/753#note_5345

I'm not sure that I agree. First, lowercase is easier to read/comprehend. Also, some orgs will use hyphens and either periods or underscores to have different meaning or parts within a file name structure.

Specifically, in the work I've done (admittedly not for a while), I've been expressly lowercasing files that are all uppercase. I preserve mixed case and other characters. That's just been my own approach though.
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/753#note_5346

You don't agree with what? The idea here is to just offer another *option* for sysops that want uploaded-filenames to conform with a specified subset of all possible characters. If the sysop wanted to backup their file areas directly to ISO-9660 media (as an example), then they might want to enforce that the filenames conform with that standard.

There already options for limiting uploaded-filename character sets. This would just be adding another option that most sysops wouldn't even know or care existed and would have no impact on them.
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)