Stop printing a message key as the legal line, and calibrate the guard

Fixkamo-marketing
Shipped
September 16, 2026 at 3:12 AM UTC
Author
Kamo
Commit
77f34a1

The footer's terms-and-privacy sentence was the only rich-text message on the site. The translation service rewrote its tags as prose in 12 of 21 locales, so t.rich got a tag it had no renderer for, threw, and the footer rendered the literal text "footer.finePrintAgreement" to more than half our visitors. It is now composed from two plain keys and a Link, reusing the nav's own label strings, the way SignupSection already does it. No markup is left for a translator to edit. The punctuation guard grows three checks with it: rich-text tag integrity, and length floors and ceilings. The length check is calibrated per locale from that locale's own fifth percentile. A first draft used one ratio for every language, and it would have failed the build on 470 perfectly good Chinese strings, including the rendering of "The All-in-One White Label Business Operating System" as ten characters. Chinese runs at a median 0.35 of the English length and Latin locales near 1.1, so a shared constant either misses real damage or condemns a whole writing system. Brand-name loss is reported rather than fatal. It is real damage, but it arrives in bulk from one bad sync, and failing the build on it would wedge every deploy behind a translation run nobody can hand-fix. The count is the signal, and it should be zero. Verified across 146 pages in all 22 locales: no missing messages, no leaked key paths, no error boundaries. Dictionary side is 479d2f1c.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing