adobegripes acrobat only the acrobat team
Acrobat: ONLY THE ACROBAT TEAM COULD MAKE AN OS FUCK UP THIS BADLY.
How is this even fucking possible?
Classic MacOS uses “:” as a path separator, while current MacOS and unix systems use “/”. If you use a “:” separator within a Unix context, it will look like a “/” in a classic Mac context (remember, Finder is a Carbon application), and vice versa. Most likely, the Adobe team used some old code from the Classic era that uses “:”, and changed it to use a new API (e g going from Toolbox code to CoreFoundation), but forgot to change the path separator convention in building the path.
Reproduce it on your own: