Quick answer — Wire copy has to be translated in minutes, not hours, so the pipeline runs automatically and a subeditor edits the output. The constraint is house style and local naming conventions, not raw translation speed.
Vitra.ai Universe turns one story into every edition.
Volume arrives faster than people
A mid-sized desk takes hundreds of agency items a day and publishes a fraction of them. Translating everything by hand is not a resourcing problem to solve — it is arithmetic that does not work. So the shape is inverted. Everything gets translated automatically, and human attention goes to what is being published rather than to what might be.
What the desk still has to do
| Task | Why it stays human |
|---|---|
| Selection | Editorial judgement about the audience |
| Headline | Rarely translates; it is rewritten |
| Local naming | Places and figures have local conventions |
| Attribution | Agency crediting rules are contractual |
| Legal read | Defamation and contempt differ by jurisdiction |
Headlines are the clearest case. A wire headline written for one market is almost never the right headline for another, so it is composed rather than translated, and translating it faithfully produces something nobody would write.
Naming conventions cause most corrections
Place names, institutions and honorifics have local forms, and a translation that uses the source form reads as foreign in a way readers notice immediately.
That is terminology work rather than translation work. A glossary holding the house form of every recurring name resolves it once instead of per story, and it is the single highest-value thing a desk can build.
Legal is jurisdictional
Contempt rules, reporting restrictions and defamation thresholds differ, and a story that is safe to publish in one country is not automatically safe next door.
Faithful translation carries the risk across intact. That belongs in the desk's workflow as a check, not as an assumption.
Running it
Document translation handles the intake at wire pace, terminology comes from memory so names resolve consistently, and quality control flags what needs a human before it reaches one.
Corrections write back, so the name a subeditor fixed this morning is already right this afternoon — which is what makes the desk faster over a week rather than only on the first story.
FAQ
Can wire copy be translated automatically? Yes, and it has to be, because volume exceeds what any desk can translate by hand. Human attention then goes to selection, headlines and legal checks on what is actually being published.
Why are headlines not translated? Because a headline written for one market is rarely the right headline for another. Headlines are composed for the local audience, and a faithful translation produces something no editor would write.
What causes most corrections in translated wire copy? Naming conventions. Place names, institutions and honorifics have local house forms, and using the source form reads as foreign immediately. A glossary settles it once rather than per story.
Does translated copy carry legal risk across borders? Yes. Contempt rules, reporting restrictions and defamation thresholds differ by jurisdiction, so a story safe to publish in one country is not automatically safe in another.
