Quote:
Originally posted by lendaddy
That's not insignificant at all. It doesn't matter whos fault it is if the problem exists. You certainly don't expect every user to know about the extensions do you? Especialy when these files get "chain-mailed" down the customer line. Like I said earlier, all they will know is that the damn file isn't opening.
Regardless, I do appreciate you explaining what was happening, I had never heard that before.
|
Len,
That was mostly back in the pre OS X days. I can't really fault the user to much since Windows apps had to append the file extension in order for the file to be associated with the correct app. The enduser did not have to do it so was not aware of its significance.
Mac users did not need the extension because the OS dealt with file associations differently so they were not aware of the significance.
All of that changed with the internet age. Now you are sending files all over the place that pass thru multiple machines along the way to their destination, usually UNIX boxes.
The only way to get the file to the other end "intact" was to fall back to the least common denominator, add a file extension.
All modern day OS's append the file extension by default. Windows hides it but it's still there. Most Mac apps show it and every one gives you the option to hide/show it which is different than the old days of include/don't include it. Regardless it's a visual thing and the actual file itself has an extension same as Windows.
The only time it should become an issue is if you send/receive in a file format from an app that the sender/receiver does not have. Example would be a .dfx from a 3D or CAD app. Not a common app for the average user.
Here's something you'll like about OS X. PDF functionality is built into the print engine. No matter what app you can make a PDF. You just send it to print and in the print dialog box is an option to create a PDF instead.
Everyone can read a PDF.