Release 3.2.0 -- ROI coding, decode and encode Region-of-interest coding, the last wholly unanalysed part of the format, is now supported in both directions. ROI changes only how a level's coefficients are partitioned into segments; everything else is identical to ordinary coding, which 1728 matched pairs establish directly. decode 1728/1728 against the reference decoder, and ROI == non-ROI encode 1728/1728 coefficient-exact against the reference's own ROI file Zero-level ROI is refused: the reference segfaults on such files, so writing one would produce output no other implementation can read. Three bitstream corrections came out of it, none ROI-specific -- a one-word payload is legal, the RAW record's slot field floors, and the RLR terminator's sign bit is 1 rather than 0. The last changes this encoder's output bytes for every format; files from earlier versions remain valid and readable, and decoding is unaffected. Not byte-identical to the reference: it writes two reserved header bytes whose meaning is unmeasured and which this encoder declines to imitate, and its significance streams are one bit longer than minimal on textured images. On a flat image, output is byte-identical apart from those two bytes. 573 tests. Specification 1.10.