Re: Couldn't open [...Filename...]
by okh » Mon Jan 22, 2018 6:20 pm
Mac users are a bit spoiled as Apple had the good sense to support long (256) file names and extended character sets from at least 20 years ago, while Win still carries a legacy from early DOS. In Win, there is still an 8+3 filename (limited ascii) for every file, not to mention a limitation in the total number or characters in a path. Which means a file moved further down the hierarchy can create havoc with the OS. I think the trouble usually occurs when files with non-std-ascii characters are moved between different platforms and operating systems. And to ensure internet compatibility, it is better to drop spaces too...
Me, I have given up: shorter file names and only a-z and 0-9 - no spaces.
ok
PS - which reminds me
1) some characters outside US ASCII would make printers go bananas, and,
2) it used to be possible to tell the difference between VAX/VMS and Unix users by whether they used underscore or hyphens instead of space...