The byte order flag applies to object data only: database pages stay
little-endian. Object data is decoded in the file's byte order, and in
big-endian data the string tag and the flag byte before it are swapped.
The two big-endian samples are also the only files from before
InDesign 7.0, and some of their layouts differ: page transform and
bounds chunks, font records, XML tag names and nodes, story strands and
40-byte guide records are read; text frame settings, document
preferences, a composite font and a section style are left out with a
warning. The 40-byte guides of an InDesign 7.0 file are now read too.
docs/format/big-endian.md records the evidence. The corpus tests now
cover all byte orders.
Select the active master page by sequence number, read the database page
count, iterate the contiguous objects after the database pages, and
extract the XMP packet. `indd info` now prints these fields.
The layout comes from Adobe's BSD-licensed XMP Toolkit SDK and is checked
against all 352 corpus files and the fixtures. Add Adobe's BlueSquare.indd
sample (BSD) as a fixture and record the XMP Toolkit as a permitted
reference.
Decode the signature, byte-order flag and InDesign version from the INDD
header, add an `indd info` command, and add smoke tests on four
open-licensed sample files plus an optional local corpus test.
Document the clean-room method and the header layout with the evidence
for each field.