A pun that only works in one language reads as gibberish once it's translated

What it is

Humor bound to a specific language and culture — puns, homophones, memes, in-group references — survives the translation pipeline at a rate near zero: literal translation preserves the words and loses the joke, and machine translation fails to register that there was a joke at all. The decisive fact is the nature of the failure product: it is not neutral plainness but noise — a sentence that is neither funny nor comprehensible, sitting in the slot where the original had a joke, reading like the product has malfunctioned. So this is not a quantitative question of "how much of the joke was lost" but of "what form the translated humor takes": under the real constraint of untranslatability, it takes the form of noise.

Why it happens

The mechanism has two layers. The language layer: a pun pivots on a sound or spelling specific to one language; across the language border the pivot is gone, while the sentence's grammar and vocabulary are faithfully carried over — the product is a structurally complete sentence waiting at the end for a punchline that never arrives. The reader processes it as a joke (position and tone both signal "something funny here"), pays the decoding cost, and is paid out in literal meaning; this promise-voided reading is nearly indistinguishable from reading a broken sentence, and users conclude the product's language is defective. The pipeline layer is more lethal: translation workflows certify fidelity — translators are told to add nothing and omit nothing, and terminology-consistency checks and quality scores all punish deviation from the source. The better the translation scores, the more cleanly the joke dies. Machine translation pushes this to the limit: it has no category for "punchline," so its literal equivalents actually score well on literal-accuracy checks. Across the whole pipeline, humor has no identity — unmarked, untreated, un-reviewed as a creative asset — making it the natural casualty of a fidelity-driven process.

Where it stops holding

The first opening is humor type: the shallower the dependence on shared context, the better the type survives the pipeline — situational humor aimed at what just happened on screen, and visual absurdity, can cross languages, while puns and dated memes cannot; the dependency hierarchy of types has its own criteria, and the translation side needs only this survival order. The second opening is replacement: transcreation rewrites the gag for the target language instead of translating it, letting humor stand up again in another locale — at the cost of commissioning and reviewing every rewrite separately, with repeated rewrites drifting the brand voice. Third, single-language products with no translation pipeline are untouched — noise is a product of the pipeline, and no pipeline means no noise.

Applying it

• Mark humorous strings as their own category in the string table, so the "this is humor" identity travels through extraction, translation, review, and sign-off; unmarked, the pipeline processes it as ordinary copy.
• Give translators replacement rights, not a fidelity obligation: the handoff brief states what the line must accomplish (ease a wait, mock the system once, soften an error), not what it says; acceptance is by whether it works in the target locale, not by literal correspondence.
• Gate humor by locale: launch a gag only in locales where native-speaker review has passed it; locales that have not passed review get the plain humor-exempt version — which must carry all critical information in full, so that humor's absence never becomes information's absence.
• Never route humorous copy through machine translation into production.
• To validate: sample native readers in every humor-launched locale and sort responses into laughed / did not get it / offended; more than one third "did not get it" rolls the locale back to the plain version. Also check the plain version itself against the source line by line for critical information, confirming the exemption did not exempt the content too.

Related

• Same group: P1.12.1 Humor may target only the system, never the user · P1.12.2 Waiting scenes carry humor better than error scenes · P1.12.3 Humor degrades the information in the same copy
• Nearby: P1.06.3 Humor is tightly bound to culture and context · S1.07 Writing for translation
• Search terms: transcreation · untranslatability · localization QA · string localization