I guess so. It is strange that noone did a good job in "explaining" concrete format architectures over the web. You just must consume 3-7 documents about selected architecture (if it is not bmp ), and exclude another 5-10 irrelevant documents, to juice out knowledge "After checking you are on Tiff header (which starts two bytes after "Exif" bytes and is header of Exif) you find pointer to first exif partition (IFD) at eight position, seek, you get number of 12-byte tag records in current IFD, first bytes of tag is ID of "name" of "value", then goes record type, then goes 4-byte pointer to value anywhere in After-Tiff section (absolute to start of Tiff header), which, if record type fits 4 bytes is not pointer but directly stored tag value. Every IFD contains tag refering to next IFD in absolute scale starting from tiff header start. (To get to Tiff header correctly find application marker xE1 in jpeg's xFF partitions).
I think all the filetype info all around is very hard to use. It should at least contain some examples in C, and also it should be divided to "Short understand", "Long understand" every internal system and then Tables sections which are too concrete to be placed in "system of" text. All which I found about Jpeg, Exif and Jfif are examples of exactly informing but not very usable(friendly) documents. For example I was turning exif pdf up - down around to find where are tags stored and how to get to them for some hours, and after guessing, that if tiff header is used in exif, I should read about IFD (importancy of IFD only I understanded from exif.pdf at moment) in tiff.pdf. I scrolled to tiff IFD section, read 1-2 paragraphs and I could return to Exif document with full knowledge of what to search and how in exif.pdf.
But maybe I would want folder-book for teaching diferencial math. who knows.
Enter your message below
Sign in or Join us (it's free).