On Sat, 25 Oct 2025 15:50:47 -0500, Charles Mills wrote: > >I completely *personally like* case insensitive filenames but I also think it >is an bottomless morass if you are defining a system that will have global >and/or Unicode usage. The list of "these two different bit patterns mean the >same thing to a human" cases is endless. > The earliest typewriters lacked keys for "0"and "1". Typists substituted "O" and "l". Should those visually similar pairs be considered equivalent filenames? Similar concerns for superscript zero and degree symbol.
Rather than burdening developers with documenting an "endless" list of n-tuples, it's better to have the simplest rule: "No different characters are equivalent." MacOS does not allow the entire printable subset of ISO8859-1 in filenames. Comment? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
