Alice Lee Poetics (李 诗诗)

    "ExifByteOrder" mostly indeed exists: similar to Unicode Byte Order Mark.     Some hint must present for byte order indication to work.     However with such information missing: the byte order can also...

    Is it sensible to make "-api [NoMandatory](https://exiftool.org/ExifTool.html#NoMandatory)" default?     People mostly wouldn't wish to unawarely write what they didn't intend.     Would such create significant problems on certain formats?

    Worth notice, many of the specs self have validity issues.     Alike: https://trac.ffmpeg.org/ticket/11002#comment:19     Nevertheless, typical readers should have no problems interpreting alike.

    Somewhat derivable.     But what about UTF-8? (1 ~ 4 Bytes per character)

    Specifically, this is likely of interest only to UTF-8.     Consider add only for UTF-8?     Perl-IO shall handle it.     https://perldoc.perl.org/perlunifaq#What-is-the-difference-between-:encoding-and-:utf8     https://github.com/exiftool/exiftool/blob/master/lib/Image/ExifTool/Text.pm

    Thanks for linking.     Though my posts are mostly for theoretical enhancement, than looking for workaround.     Clarification:     The suggestion is more focused on printing.

    "(Binary data 768 bytes, use -b option to extract)"     The interpreted display is regardless susceptible to change.     And this one would be mostly just verbatim copied.     Perhaps displaying the parsed...

    When [Orientation](https://exiftool.org/TagNames/EXIF.html) = "Horizontal": stripping it should be alright.

    The CommonIFD0 name already indicated it shall overkill and possibly wreak havoc.     Whatsoever, if "-*=" already included CommonIFD0: most wouldn't even bother knowing it.     Many use ExifTool typically for file...

    "-*=" probably wouldn't be expected as safe way whatsoever...