exiftool-vendored
Advanced tools
Changelog
v23.2.0
✨ Timezone parsing improvements:
ExifToolOptions.inferTimezoneFromDatestampTags
.📦 Add creationDate
to CapturedAtTagNames. See PR#159.
Changelog
v23.1.0
🌱 ExifTool upgraded to v12.67
✨ ExifTime
now parses and stores timezone offsets if available. This resolves issue
#157.
📦 ExifDateTime
, ExifTime
, and ExifDate
are now only allowed to try
to parse keys that includes date
or
time
,
which avoids incorrect parsing of tags like MonthDayCreated
(which looks
like 12:19
)
📦 Updated all dependencies, but only devDependencies
were impacted.
Changelog
v23.0.0
🏚️ Dropped support for Node.js v16, which is End-of-Life.
💔/🐞 If defaultVideosToUTC
is set to true
, read()
will now allow non-UTC
timezones extractable from other tags to be assigned to .tz
. Prior
versions would simply force .tz
to "UTC" for all videos, which wasn't
great. Note that "UTC" is still used as the default timezone for all
datestamps without explicit timezones, just as prior versions did. See issue
#156 for
details.
💔 backfillTimezones
now defaults to true
. Although this is likely to be
what people expect, but know that this makes the assumption that all encoded
times without an explicit offset share the same tz, which may not be correct
(say, if you edit the image in a different timezone from when it was
captured).
💔 If backfillTimezones
is set to false
, ExifDateTime
will no longer
use the current file's .tz
as a default. Prior versions would inherit the
file's .tz
, which might be incorrect.
📦 ExifDateTime
now includes an .inferredZone
field, which may be useful
in helping to determine how "trustworthy" the zone and actual datestamp
value is.
Changelog
v22.2.3
SubSecTime
value of "01" in the wild, and it was happily parsed into today's date, oops).Changelog
v22.2.2
/^0+$/
.Changelog
v22.2.1
ExifTime
now properly rejects invalid SubSecTime
, SubSecTimeOriginal
, ... values of "0" or "00".