We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
exiv2 allows the user to set invalid dates, such as those in the common format YYYY-mm-dd HH:MM:SS.
In EXIF the dashes must be colons instead. exiv2 doesn't check this, allowing the user to set an invalid date without any warning.
Find any JPEG file and copy it to test1.JPG
$ x=test1.JPG $ d="2023-07-21 21:06:26" $ exiv2 \ -M "set Exif.Image.DateTime $d" \ -M "set Exif.Photo.DateTimeOriginal $d" \ -M "set Exif.Photo.DateTimeDigitized $d" \ "$x"
exiv2 should not let me set date strings that are not formatted correctly as per the EXIF specification, at least not without a clear obvious warning.
Additionally, exiv2 should print warnings about invalid dates. At the moment, this doesn't occur even with -v.
-v
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
exiv2 allows the user to set invalid dates, such as those in the common format YYYY-mm-dd HH:MM:SS.
In EXIF the dashes must be colons instead. exiv2 doesn't check this, allowing the user to set an invalid date without any warning.
To Reproduce
Find any JPEG file and copy it to test1.JPG
Expected behavior
exiv2 should not let me set date strings that are not formatted correctly as per the EXIF specification, at least not without a clear obvious warning.
Additionally, exiv2 should print warnings about invalid dates. At the moment, this doesn't occur even with
-v
.Desktop (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: