exiftool-vendored
    Preparing search index...

    Variable DefaultReadRawTaskOptionsConst

    DefaultReadRawTaskOptions: {
        ignoreMinorErrors: boolean;
        readArgs: string[];
        useMWG: boolean;
    } = ...

    Type Declaration

    • ReadonlyignoreMinorErrors: boolean

      Should we ignore minor errors when reading metadata?

      true (ExifTool can be quite chatty)
      
    • ReadonlyreadArgs: string[]

      Any additional arguments that should be added by default to all read tasks, like ["-fast", "-api", "largefilesupport=1"]. The value provided to the ExifTool constructor can be overridden in the call to ExifTool.read.

      Security: entries are passed through to the underlying exiftool process verbatim. Never pass attacker-controlled strings here. The library rejects any entry containing \r, \n, or \0 as a defense-in-depth measure, but provides no other sanitization.

      JSON reads repair malformed UTF-8 with U+FFFD () independently of this array and preserve the original string bytes in Tags.invalidUtf8Bytes. If these arguments contain an explicit, non-empty ExifTool -api Filter=... option, that custom filter owns the complete output filtering pipeline and must perform any desired UTF-8 repair and byte capture itself.

      The marker appears only in string values; to render it as the pre-v37 ?, post-process with typeof value === "string" ? value.replace(/\uFFFD/g, "?") : value.

      ["-fast"]

    • ReadonlyuseMWG: boolean

      Should ExifTool use MWG (Metadata Working Group) composite tags for reading and writing tags?

      ExifTool recommends this to be set to true. Note that this can result in many tag value differences from ExifTool.read, and makes ExifTool.write write to "synonymous" MWG tags automatically.

      true