|
|
Damaged how?
That is my point exactly, other programs now know what to do with them. Other programs know how to modify jpegs. My hunch is that apple did not make them jpegs on purpose so that other programs didn't modify your photos. This way you have "negatives" that you can always go back to. If you want to play with your photos as jpegs, iPhoto allows you to export them as jpegs. Why else would they not have made them file type JPEG? On accident? I doubt it, these are jpg files we are talking about. I understand what this workaround is talking about, I just don't think that it's a good idea.
Damaged how?
All right, let's think here people. If Mr. Jobs had really wanted to intentionally "obfuscate" the files' metadata, such that other applications could not as easily "tell" they were indeed jpeg images, don't you think the software might also have gone so far as to remove the more-obvious ".jpg" extensions on the files? At least in my iPhoto library, most of the JPEG files I've imported were simply renamed to xx.jpg, though the type code is stripped off.
Damaged how?
Come on, this smacks of a bug in iPhoto (or iMovie's importing routine) rather than a conscious attempt to stop other apps from importing them. |
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.16 seconds |
|