Repository navigation
Vision OCR 1.13.0 — pale drawings and photographs come out intact
The two ways Automatic could destroy what was on a page — both listed as known in 1.12.0's notes — are fixed. If you kept a document in Grayscale to stay clear of them, you no longer need to.
A photograph could come out as a solid black shape. A continuous-tone plate covering roughly a fifth of a sheet was thresholded to pure black and white, taking the line of text above it with it. It slipped past two separate checks at once, because a picture that large dilutes its own tone across the page and both limits had been calibrated on pages a picture dominates. The page's tone is now measured inside each large mark rather than across the whole sheet — the same test, asked about the right region. Found on real pages, not in theory: a credited art photograph in one book was rendering as a blob, and one thesis in the test library had 87 more.
A pale line drawing could be erased. Not blurred — gone, with the text beside it untouched, which is what made the result look fine. Faded ink, light pencil, a pale wash. Four attempts to fix this by brightness were built and refused, because the range of tones too light to be ink and too light to be a photograph holds three different things: drawings you want kept, decorative shading you do not mind losing, and show-through from the back of the sheet you actively want gone. No brightness test separates those. What separates them is where the mark is — show-through lands on top of the page's own type, because it is type seen from behind, while a figure sits where the type is not.
Pages no longer borrow their resolution from a neighbour. On documents whose pages share one internal resource list, a page could be rebuilt at whatever resolution the largest image anywhere in that list implied — so in one journal article every page of type was rendered at 370 DPI because page 41 has a plate on it. The app now looks at what each page actually draws. 130 pages across the test library changed, every one of them measured, and the affected documents come out smaller with the same words recovered.
Three smaller things you might have noticed:
- A line of text you could not highlight — a whole line could be drawn at 5% of its width.
- Words welding together when one part of a line was much shorter than the next.
- A rebuilt copy showing something the original had hidden at the edge of the sheet.
Requires macOS 13 or later. Unsigned by choice: System Settings ▸ Privacy & Security ▸ Open Anyway after the first launch attempt.
How this one was checked
Every document in the test library went through the whole app before this shipped: 233 of 233 succeeded, 0 failed, 16,987 pages, 34.2 million characters. Every output was then compared against its original pixel by pixel, not by its text — a check added after an earlier release gate proved it could pass a page whose image had been destroyed.
Forty pages came back flagged and none of them was a fault. Thirty-five are pages that are near-blank in the original and near-blank in the copy. Five were flagged for looking unlike their originals, and three of those were rendered and looked at by eye rather than trusted to the score: a dedication page reading "For Rosie", an Internet Archive boilerplate page, and a two-page spread of body type. In all three every word survives, including one copyright page's fine print, and what fell away was a grey scan background or a pale decorative watermark. That is the score's shape, not a defect — on a page whose entire content is two words, cleaning the paper changes almost every pixel while losing nothing.
The defect register behind this release is empty for the first time: 0 open of 163 entries. Every fix above is written up with its evidence in BUGS.md, including the fixes that were built, measured and refused.