MindBender
Guru
- Messages
- 611
- Likes
- 0
1. That doesn't apply if you're going from windows to windows as there isn't any meta data stored.
2. The meta data that is stored in the resource fork only contains the system data about things like creation program and such. Since windows uses an internal registry rather than a file system tracking, it's not needed for sending files to windows. Since programs like photoshop will recognize files based on file name extensions and data fork, again, the meta data isn't needed even on a mac.
3. When you strip the meta data from a file it becomes smaller, this is good practice when putting files online anyway, so you'd end up a lot of that data being stripped away anyway.
4. That information only applies to mac os 9 and previous. OS X doesn't use resource forks for it's data anymore. It's all held in package information as part of the file now.
5. Using encoding doesn't eliminate the possibility of corruption on either system. It simply keeps the mac classic meta data available. Compressed files can be corrupted just as easily as any other file. When you get a file that's corrupted off the internet the causes are usually plain old file system corruption on the file server, or file corruption due to a bad data stream from the server. Neither one of these things are prevented by encoding. The only advantage that encoding offers in that case is allowing you to add things like checksums so that you know if the file has become corrupted. This is why most self extracting installers run a verify process first (default for any dmg on max os x). Sometimes this works against you though. I've often had images that I needed. If the archive file was corrupt, I would lose all of my data. But since things like jpegs are linear data, you can often save portions of a corrupt file by opening the viewable area and moving the good portion to a new image.
6. Most modern systems know how to deal with mac, pc, unix, linux, solaris, sparc, vax vms, whatever. The golden age of file incompatability is slowly receeding.
7. This applies not to you but to compressed files in general. Compressed files and especially self extracting files are a great place to hid malicious content. You get an image... and some trojan or virus has latched itself onto the file. There are even viruses that are specifically designed to open, infect, and re-close zip files. This is less of a problem on mac os 9 and previous due to the lack of viruses on those systems, but since mac os x is based on BSD, there are more viruses appearing on that system. We've even seen the first cross platform mac/windows virus in the last couple years. Windows users have always been plagued by virus problems though. heh
8. ...
What was it that Aladdin does again? Stuffit? Isn't that some sort of compression and encoding program that they sell... of course they want you to encode everything!
hehe
Yes, encoding does offer some advantages, but it's not a unilateral choice.
2. The meta data that is stored in the resource fork only contains the system data about things like creation program and such. Since windows uses an internal registry rather than a file system tracking, it's not needed for sending files to windows. Since programs like photoshop will recognize files based on file name extensions and data fork, again, the meta data isn't needed even on a mac.
3. When you strip the meta data from a file it becomes smaller, this is good practice when putting files online anyway, so you'd end up a lot of that data being stripped away anyway.
4. That information only applies to mac os 9 and previous. OS X doesn't use resource forks for it's data anymore. It's all held in package information as part of the file now.
5. Using encoding doesn't eliminate the possibility of corruption on either system. It simply keeps the mac classic meta data available. Compressed files can be corrupted just as easily as any other file. When you get a file that's corrupted off the internet the causes are usually plain old file system corruption on the file server, or file corruption due to a bad data stream from the server. Neither one of these things are prevented by encoding. The only advantage that encoding offers in that case is allowing you to add things like checksums so that you know if the file has become corrupted. This is why most self extracting installers run a verify process first (default for any dmg on max os x). Sometimes this works against you though. I've often had images that I needed. If the archive file was corrupt, I would lose all of my data. But since things like jpegs are linear data, you can often save portions of a corrupt file by opening the viewable area and moving the good portion to a new image.
6. Most modern systems know how to deal with mac, pc, unix, linux, solaris, sparc, vax vms, whatever. The golden age of file incompatability is slowly receeding.
7. This applies not to you but to compressed files in general. Compressed files and especially self extracting files are a great place to hid malicious content. You get an image... and some trojan or virus has latched itself onto the file. There are even viruses that are specifically designed to open, infect, and re-close zip files. This is less of a problem on mac os 9 and previous due to the lack of viruses on those systems, but since mac os x is based on BSD, there are more viruses appearing on that system. We've even seen the first cross platform mac/windows virus in the last couple years. Windows users have always been plagued by virus problems though. heh
8. ...
What was it that Aladdin does again? Stuffit? Isn't that some sort of compression and encoding program that they sell... of course they want you to encode everything!
heheYes, encoding does offer some advantages, but it's not a unilateral choice.