I think I have a better one.
I was trying to download some software from a Japanese website (this was about 10 yrs ago I think). There was an entire survey you had to fill out first. Since I speak no Japanese, I naturally used Google Translate (to Polish, not even to English).
That survey had a "gender" field, and the options were something like "person" and "woman".
Then there are the automatic (mis)translations of button labels and other similar strings in software, where the translating tool often only has a single and ambiguous word to go on, with no context whatsoever.
THe funniest ones I've seen are "branch" (satellite office) versus "branch" (of a tree), "book" (a flight) versus "book" (something you read), "character" (ASCII or Unicode) versus "character" (in a story), "clear" (to remove all) versus "clear" (translated as "cloudless", referring to the sky), "letters" (delivered by a postman) versus "letters" (and not digits), "rate" (how fast. i.e. speech rate) versus "rate" (how much you charge per minute), "prune" (remove all) versus "prune" (dried plum), "manual" (and not automatic) versus "manual" (a user manual), "clubs" (places you go to) versus "clubs" (and not diamonds or spades, "queen of clubs" hav a particularly interesting meaning here), "number" (that you call) versus "number" (of things), "at" (@) versus at (home), "tab" (key) versus "tab" (in a browser), "close" (to me) versus "close" (something), "back" (button) versus "back" (a body part), as well as all the "party" (adventuring team in an RPG) versus "party" (legal entity, i.e. "third party") versus "party" (as in an event you have fun at) shenanigans.
Mistakes like these often hide in accessibility labels, and are hence far more obvious to screen reader users. In normal UI, they're usually found quickly enough that users never notice, but accessibility labels are often overlooked when testing translations.