By Jeff Steele
Continued from Page 1...
So, you ask, what happens when these oh-so-differently marked files go to their respective darksides?
This is where the fun begins. Apple, in it's infinite wisdom, knew that there would be a significant amount of file exchanges taking place between Mac's and PC's. So, to facilitate this, they built the MacOS so it can recognize the three digit extensions tacked on to PC files. Basically, if a file on the Mac doesn't have file type and creator codes, it can use the three digit extension to figure out what kind of file it is dealing with. The Mac can also read (and format) PC media such as floppy diskettes, Zip disks and CD-ROMS, which makes exchanges much easier.
On the other hand, the PC is unable to read the file type and creator codes in the resource fork of a Mac file. Therefore, if the file doesn't have a three digit extension, the PC has no idea what to do with the file. Furthermore, the PC is not capable of reading Mac formatted media without special third party software utilities.
Don't get me wrong here. I am not trying to imply that one system is better than the other. Simply put, Apple designed more system-level support for cross platform transfers into the OS than Microsoft.
Now, let me throw one more wrench in the works. Let's say you are working on a Mac and you need to e-mail a file to another Mac user. You write a quick e-mail, attach the file and send it on it's merry way. A few minutes later, the other designer calls you and says, "What the ****(censored) is this?". You, unaware of the havoc that has been wreaked on your file, stutter an incomprehensible response about the questionable parentage of your computer.
Let's take a quick look at the fate of that poor file. As soon as you e-mailed the file, it went out over your network, which is most likely a Windows-based network. When your poor attached Mac file hits that first Windows-based server, the server looks at the attached file and finds something that it doesn't recognize. "What is this 'Resource Fork' thing attached to this file?" it says to itself with a slight British accent. Finding no reasonable use for the resource fork, the server promptly strips that portion of the file away and sends our poor hero (sans resource fork) on to the lucky recipient, who, upon attempting to open the file, is presented with a message asking exactly what application they would like to open this unknown file with and if, perhaps, you would enjoy a spot of tea.
Put simply, Windows-based networks have a bad habit of stripping the resource fork from Mac files and leaving them without any form of ID whatsoever. There is a very easy way to avoid this particular problem. If you Stuff your files (using Stuffit from Aladdin), your files will arrive intact and ready to use. If you don't have Stuffit available, simply apply the proper 3 letter extension to the file so that when it does arrive at it's destination, it is at least partially recognizable.
So here is what it all comes down to. When you create a file that is bound for another computer or another platform altogether, always use a three digit extension to identify the file. That way, regardless of where the hapless file may find itself, it can be identified by it's host system and recognized for what it truly is. Happy ending.
But wait! There's more! If you order in the next 13 minutes.....wait, wrong article... Seriously, there are a few other minor issues to watch out for when crossing the great platform divide.
Related Information 
- Cross-Platform Tips & Tricks
- Converting Images
- Cross-Platform File Naming
- Mac-Windows Integration
- Graphics File Formats
- Macintosh Cross-Platform Software
- PC and Windows Cross-Platform Software
