There's not much you can do to get around the problem without teaching the clients new tricks.
Windows machines know nothing of reading/writing Mac-compatible resource forks.Ģ) The files originated on a Mac, but were either transferred with a protocol or compressed with a program that ignores or strips files of that resource fork information. doc extension to associate the file with Word.ġ) The files originated from a Windows machine (or some non-Apple operating system) and no extension was put on the file. This doesn't happen with files with extensions most of the time, because even if a Word document lost its resource fork (type/creator codes, specifically) information, it could still use the. What's happening is that Mac OS X can't read the file's resource fork (and, since there's no extension on those files either, it can't even "guess"), and therefore doesn't know what the file is.
0 kommentar(er)
