|
|
Why? seems like a bad idea
I'm curious, Why do you want to do this? seems ill advised. this loses all the meta infromation about the files, like their icons, creator app, etc...
Why? seems like a bad idea
When you email a document to PC users, their machines have *no idea* what to do w/ a resource fork.
Why? seems like a bad idea
MacDork - people often use this technique to slim down filesizes on images used on web pages. The mac image files have a small bit of overhead size 2-8k or so for each image for ther resources. They are useless in web applications - so why not trim the fat. I supposed there may be other uses for this technique too, but thats probably the most common I suspect.
Why? seems like a bad idea
There are a few reasons why you may want to strip the resource fork. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.10 seconds |
|