![]() This would be information such as "this is a JPEG file created by Adobe Photoshop" that the original Mac OS needed to open files, and that Mac OS X still consults when opening them. It seems that the second file (the one whose name begins with ".", and which contains the resources), also contains Finder metadata. Thanks Tom_N, but your explanation is a bit too technical for me. (You can tell that people who build TVs are not always big on descriptive error messages.) So the jpg decode fails and the TV goes, "". jpg file it is a stub representing the resource fork (and maybe also metadata like the type/creator codes?) associated with "CatPhoto.jpg". ![]() My guess is that it sees the ".jpg" extension on (e.g.) ".ĬatPhoto.jpg" and tries to process the file as a. I'm guessing that you might get that second file even if there was no resource fork data to copy into it.Īs for "", I suspect that this is the way the TV chooses to display error messages. "CatPhoto.jpg" (data fork of the Mac's "CatPhoto.jpg")ĬatPhoto.jpg" (resource fork of the Mac's "CatPhoto.jpg") On a non-Mac filesystem like FAT32, you would get Internally it would have a structure to support two 'forks' or sub-files (though perhaps here, only the data one would be in use). On the Mac HFS+ filesystem, a file ("CatPhoto.jpg") that had data and resource forks would not have two separate names. Trying to sort this out has dragged on for over 3 months. This can only mean that the Mac is restoring a Resource Fork to each image file after GraphicConverter has removed the one that was there. And, although my TV was saying that the image files on the SD card were still interleaved with Resource Forks, at his end the Resource Forks were shown to have been removed after processing with GraphicConverter. We had what is called a Team Viewer session which enabled him to see my desktop. So I contacted the writer of the software in Germany. I downloaded and installed a software Application called GraphicCoverter, which has an option for removing Resource Forks from files.īut Resource Forks still showed up on the TV after processing with this software. The TV operating system sees them, but has no use for them. Įach, I have discovered, represents an additional file of information called a Resource Fork, generated by, but always invisible on, Macs. When I wish to view photos on an HD TV from an SD card, the experience is spoiled because between every image is another, unusable one, looking like this.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |