On Sat, 25 Oct 2025 at 17:33, Paul Gilmartin <
[email protected]> wrote:
[...]
> MacOS does not allow the entire printable subset of ISO8859-1 in
> filenames. Comment?
>
Neither does Windows. And if Windows filenames are being mapped to MS
OndDrive or Sharepoint things get much more restrictive, because Microsoft
seems to have conflated such filenames with URLs with their different
restrictions. It gets even worse, because there are different rules for
OneDrive for Home vs OneDrive for Work or School. There are endless online
"guides" and "best practices", but the underlying rules seem to change at
Microsoft's whim. Certainly the characters : ~ " # % & * : < > ? / \ { |
} are going to fail in most Windows contexts, though Sharepoint has
evidently been updated to allow some or all of # % &. Or rather, to allow
an administrator to decide to allow them. And some of these characters will
be ignored when Windows is building an index for searching. Perhaps because
Office files may be automatically renamed for your convenience:
-
Filenames that contain *,* are changed to *^J*
-
Filenames that contain *#* are changed to *^N*
-
Filenames that contain *&* are changed to *^0*
-
Filenames that contain *~* are changed to *^F*
But only Office files, so you can keep those characters in other files (but
they won't be indexed). Probably. Maybe.
Your basic dog's breakfast.
Tony H.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
