17 January, 2021

Paul is Dead: How Translation Murdered a Meatball

In 1969, a rumour swept across America that Sir James Paul McCartney — bassist, songwriter, and left-handed Beatle — had died in a car accident in 1966 and been secretly replaced by a lookalike.  The evidence was elaborate: backwards-masked lyrics, album cover symbolism, the bare feet on the Abbey Road crossing.  The world was briefly convinced that one of the most recognisable men on earth had been substituted without anyone noticing.  The meatball did not intend to revive this conspiracy.  But language, as usual, had other plans.

The Translation Problem

A meatball — that cheerful, spherical product of minced meat and ambition — was transliterated into Arabic as “بول ميت” (mayt bul).  The transliteration captures the phonetic approximation of the English word.  “Bul” for ball.  “Mayt” for meat.  Standard enough, if you are working purely in sound rather than meaning.  The problem arrived on the return journey.  When “بول ميت” was translated back into English, the translator — confronted with two Arabic words that meant nothing in isolation — reached for the nearest phonetic equivalent in English vocabulary.  “Mayt” became “dead.”  “Bul” became “Paul.”  The meatball became a deceased Beatle.  “Paul is Dead.”  Fifty years of conspiracy theory, accidentally resurrected by a food label.

The Two Varieties of Translation

All translation operates along a spectrum between two poles.  The first is literal translation — the word-for-word rendering that preserves the surface form of the original at the expense of its meaning.  Literal translation is technically faithful and practically useless.  It is the approach that gives us “it rains cats and dogs” rendered in French as “il pleut des chats et des chiens” — which a French speaker receives as a meteorological catastrophe involving falling animals rather than a weather observation.

The second is intentional translation — the rendering of what the speaker meant rather than what they said.  A good intentional translation of “it rains cats and dogs” produces “il tombe des cordes” — “ropes are falling” — which captures the idiom’s function without preserving its imagery.  The words are different.  The meaning is identical.

A skilled translator straddles both.  They preserve the surface form where it is culturally legible and abandon it where it is not.  They ask: what did the speaker intend, and what words in the target language convey that intention to a native speaker?  The meatball's translator asked neither question.  They performed a mechanical reversal of a phonetic transliteration and arrived at a conclusion that would have alarmed both Sir Paul McCartney and anyone expecting lunch.

Transliteration: The Specific Trap

Transliteration is not translation.  This distinction is critical and consistently ignored.  Translation converts meaning from one language to another.  Transliteration converts sound from one script to another.  A transliteration of “meatball” into Arabic renders the phonetic approximation of the English word using Arabic letters.  It does not translate the concept of a meatball.  It does not produce the Arabic word for meatball, which is “كُفتة” (kufta) or “كُرة اللحم” (kurat al-lahm), depending on the regional context.

Transliterations are not words in the target language.  They are approximations of sounds from the source language, wearing the target language’s clothing.  When a translator subsequently treats a transliteration as if it were a native word — decomposing mayt bul into its apparent Arabic components and translating those components back into English — the result is not a translation.  It is an etymology experiment conducted by someone who did not know they were doing linguistics.

Mayt” (ميت) does mean “dead” in Arabic.  “Bul” (بول) does mean “Paul” — or more precisely, it is a common Arabic rendering of the name Paul, as in the Apostle.  The translator saw two words that had Arabic meanings and translated them.  The fact that those “words” were never intended as Arabic vocabulary was not apparent from the text alone.

This is the fundamental hazard of transliteration: it produces strings of characters that look like words in the target script but carry none of the semantic content of actual words.  A human translator working with context recognises the problem.  A mechanical process — or an inattentive human — does not.

The Broader Implication

The meatball incident is amusing.  Its implications are not uniformly so.  Medical and legal translation operates on the same spectrum between literal and intentional rendering — and the consequences of mechanical transliteration in those contexts are rather more serious than a deceased Beatle on a food label.  A pharmaceutical instruction sheet, transliterated rather than translated, can produce dosage errors.  A legal contract translated literally rather than intentionally can produce obligations that neither party intended.

The Arabic language presents a specific complication that amplifies the risk.  Written Arabic conventionally omits short vowels — the diacritical marks that distinguish, for example, between “kataba” (he wrote), “kutiba”(it was written), and “kitab” (book).  A competent Arabic reader infers the correct vowels from context.  A mechanical translation system has no context. It guesses — and in a language where a single three-letter root can produce dozens of semantically distinct words depending on vowel pattern, guessing is expensive.

The meatball’s translator guessed wrong.  The result was a food label that unwittingly revived a conspiracy theory and demonstrated, with comic precision, exactly what happens when the mechanics of language are separated from its meaning.

The Standard a Good Translation Must Meet

A translation succeeds when a native speaker of the target language receives the same meaning as a native speaker of the source language.  Not the same words.  Not the same structure.  The same meaning.  The meatball’s Arabic transliteration failed this standard on the forward journey — not because “mayt bul” is wrong as a phonetic approximation, but because it created a string of characters indistinguishable from native Arabic vocabulary.  The backtranslation failed this standard on the return journey because the translator did not ask: does “Paul is Dead” make sense as a food label?  It does not.  Sir Paul McCartney is, as of writing, very much alive and in good health at 83.  The meatball, presumably, was also doing well before the translation intervened.

The best translation is the one that makes the translator invisible — where the target language reader has no awareness that they are reading a translation at all.  The worst translation is the one that makes the translator visible in the most spectacular way possible.  “Paul is Dead” is the most visible translation mistake in the history of Italo-Swedish cuisine.  The Beatles, at least, would have appreciated the irony.


Terence Nunis, DTM | Division Advisor, District 80 Division M | Club Advisor, AIA Toastmasters | Past President & Founder, Awesome Toastmasters




No comments:

Post a Comment

Thank you for taking the time to share our thoughts. Once approved, your comments will be poster.