Exiftool adds non-mandatory YCbCrPositioning tag

[pkrause1980]

Exiftool adds non-mandatory YCbCrPositioning tag

[StarGeekSpaceNerd]

Ignore previous response if seen, misunderstood the question.

I'm still looking over the specs, though Phil might be quicker on the subject, but the relevant line might be this from page 36 of the EXIF 3.0 standard, section 4.6.1. There it mentions tags that might be mandatory in the TIFF standard.

I think the relevant part of the TIFF 6 specs is page 94.
Screenshot of the section

[boardhead]

You're right about this. It is manditory for JPEG and YCC TIFF images, but actually not allowed for chunky and planar TIFFs.

Mandatory tags are a huge pain in the ass. I don't understand why there can't just be default values if they don't exist. The problem is that the code will need a re-work to write this conditionally based on the type of the image. :(

• Phil

[pkrause1980]

Until a better fix is available, the adding of the tag could be suppressed if the "-ignoreMinorErrors" switch, or some new one(s), is given.?
It is doubtful to me to declare this a non-minor error.
The drawback is that extending -ignoreMinorErrors would be another backward-incompatible change.

[pkrause1980]

To go further, I'd prefer two things.

1. These tags should not be added automatically too, apart from ExifVersion maybe.
   IFD0:XResolution
   IFD0:YResolution
   IFD0:ResolutionUnit
   ExifIFD:ExifVersion
   ExifIFD:FlashpixVersion
   ExifIFD:ColorSpace

2. Even if mandatory tags are handled correctly, add as few mandatory tags as possible if the user request so.

Anyway, Thanks a lot!

[boardhead]

I was planning a release for today and didn't have time to fix this properly (not sure if it is worth that effort), so instead I have added an API NoMandatory option https://exiftool.org/ExifTool.html#NoMandatory to allow you to bypass the creation of all mandatory tags in EXIF.

• Phil

[boardhead]

I'll close this as complete since the NoMandatory option was released in version 12.71

[CHO1O]

OMG stop slumming me!!!

…

On Wed, 3 Jan 2024 at 18:03, Phil Harvey ***@***.***> wrote: Closed #236 <#236> as completed. — Reply to this email directly, view it on GitHub <#236 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BBOCTIUB5HZU4265NBKZIWLYMVXMNAVCNFSM6AAAAABA5DU5C6VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRGM4DAMJUHAZDANA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[StarGeekSpaceNerd]

OMG stop slumming me!!!
…
On Wed, 3 Jan 2024 at 18:03, Phil Harvey @.> wrote: Closed #236 <#236> as completed. — Reply to this email directly, view it on GitHub <#236 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/BBOCTIUB5HZU4265NBKZIWLYMVXMNAVCNFSM6AAAAABA5DU5C6VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRGM4DAMJUHAZDANA . You are receiving this because you are subscribed to this thread.Message ID: @.>

There's nothing we can do. You are getting emails from this because GitHub automatically will send you notifications to any repository you "Watch". The email literally has an unsubscribe link. Click that and you won't get any more emails.

Or in the upper left corner, click the "exiftool" link on the right, and click "Unwatch" in the upper right. You can change notification settings there or stop watching this repository.