Couldn't open [...Filename...]

[kollmerized]

Yesterday I made a plan on my iMac. Today I wanted to open and adjust it on my Win10. But i cannot open the file. There is a Error Message which only says "Couldn't Open "Filename"..."

Do you have any idea what the issue might be?

[kollmerized]

problem solved. the filename contained a "ü", this was why sweethome wasn't able to open the file.

[okh]

[:)] Sigh. In front of me there is a 8000+ file historical library collected and scanned by different enthusiasts on all sorts of different platforms and OS. French, German and Scandinavian file names. Unfortunately, using 'special' characters still means trouble. BUT there are some clever renaming and batch file manipulation software packages to clean up entire document libraries. Very powerful and handy when used with care. ok

[Puybaret]

Strange issue [:(]
I just tried with a file named ü.sh3d and didn't have any problem...

[okh]

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...