From: Greg 'groggy' Lehey <grog@lemis.com>
To: John Cowan <cowan@ccil.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>,
Bakul Shah <bakul@iitbombay.org>
Subject: [TUHS] Bugs, Bööge and Bogeymen (was: 70th anniversary of (official) programming errors)
Date: Sat, 19 Jun 2021 17:57:35 +1000 [thread overview]
Message-ID: <20210619075735.GQ23809@eureka.lemis.com> (raw)
In-Reply-To: <CAD2gp_So8VQE4ApVSAHmNgQOKNGbaBbaizovxweu2+DJnx-NKQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1883 bytes --]
On Friday, 18 June 2021 at 16:19:37 -0400, John Cowan wrote:
> On Wed, Jun 16, 2021 at 5:57 PM Steffen Nurpmeso <steffen@sdaoden.eu> wrote:
>
>> (Only to clarify that ???bögge??? is not a German word to the best of my
>> knowledge. I was looking, as it sounded so »northern«,
>
> And so it is: it's Low Saxon, and also exists in the compound form
> "böggel-mann", plainly cognate to British English "bogeyman", American
> English "boogeyman".
Well, there are ways to check these things, especially since Steffen
came up with alternatives. As they say, âWas weià Duden?â.
From https://www.duden.de/rechtschreibung/Boeoegg:
wohl gekürzt aus älter schweizerisch Böggelmann, Bölimann =
Schreckgestalt, Kobold, Herkunft ungeklärt; vgl. als ähnliche
Bezeichnung englisch bog(e)y (man) = Schreckgespenst, litauisch
bužỹs = (ausgestopfte) Schreckgestalt
In other words, a Swiss German word with a derivation similar to what
you expected. I hadn't expected that (the Swiss connection). The OED
entry is way out of date (1887) and has nothing useful to say except:
Found in literature only recently; old people vouched (1887) for its
use in the nursery as early as 1825, but only as proper name (sense
1). Possibly a southern nursery form of bogle , boggle , and boggard
, or going back like them to a simpler form which, as mentioned
under bog n.1 and bogle n., may be a variant of bugge , bug n.1
âterror, bugbear, scarecrowâ. But in the absence of evidence,
positive statements concerning its relation to these words cannot be
made.
Greg
--
Sent from my desktop computer.
Finger grog@lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 bytes --]
next prev parent reply other threads:[~2021-06-19 7:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 22:16 [TUHS] 70th anniversary of (official) programming errors Steffen Nurpmeso
2021-06-15 22:54 ` John Cowan
2021-06-15 23:44 ` Dan Cross
2021-06-16 3:48 ` Rob Pike
2021-06-16 4:13 ` Bakul Shah
2021-06-16 21:57 ` Steffen Nurpmeso
2021-06-18 20:19 ` John Cowan
2021-06-18 21:00 ` Steffen Nurpmeso
2021-06-18 22:59 ` Steffen Nurpmeso
2021-06-19 13:34 ` Harald Arnesen
2021-06-19 13:39 ` Niklas Karlsson
2021-06-19 7:57 ` Greg 'groggy' Lehey [this message]
2021-06-19 15:48 ` [TUHS] Bugs, Bööge and Bogeymen (was: 70th anniversary of (official) programming errors) Steffen Nurpmeso
2021-06-19 15:52 ` Niklas Karlsson
2021-06-19 16:36 ` Steffen Nurpmeso
2021-06-19 21:05 ` Harald Arnesen
2021-06-20 3:30 ` arnold
2021-06-16 1:06 ` [TUHS] Bug etymology " Greg 'groggy' Lehey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210619075735.GQ23809@eureka.lemis.com \
--to=grog@lemis.com \
--cc=bakul@iitbombay.org \
--cc=cowan@ccil.org \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).