The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: John Cowan <cowan@ccil.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>,
	Bakul Shah <bakul@iitbombay.org>
Subject: Re: [TUHS] 70th anniversary of (official) programming errors
Date: Fri, 18 Jun 2021 23:00:47 +0200	[thread overview]
Message-ID: <20210618210047.5uogF%steffen@sdaoden.eu> (raw)
In-Reply-To: <CAD2gp_So8VQE4ApVSAHmNgQOKNGbaBbaizovxweu2+DJnx-NKQ@mail.gmail.com>

John Cowan wrote in
 <CAD2gp_So8VQE4ApVSAHmNgQOKNGbaBbaizovxweu2+DJnx-NKQ@mail.gmail.com>:
 |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".  Or borrowed one way or the other: there is so much
 |borrowing and convergence in the Germanic languages around the North and
 |Baltic Seas that if we did not know the older varieties of these languages
 |we would never be able to work out just how they are related.

This surely leads to nowhere without going into detail, and that
is hard in respect to the dramatical losses that happened on
archives etc., due to whatever reason.  You may confuse personal
opinion.  That happens.

To me it sounds rather like a modification of "Bogen", which can
mean quite some different things itself, from a "bend" (so the
profession of a wood-bender comes to mind at a glance, "böge" is
also the conjugation of "bending" "er böge" thus "he would bend"),
also the weapon "bow", so they could have been happy producers or
unhappy consumers of such things as well.  Of course a "Bogen" is
also needed to play a Violin but putting some strings while
a thunderstorm approaches, hm, so i stay clear from that, i "make
a Bogen around it".  Given how many right politicians have that
name, i let it be good for now.

Cheerio,

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

  reply	other threads:[~2021-06-18 21:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-15 22:16 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 [this message]
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             ` [TUHS] Bugs, Bööge and Bogeymen (was: 70th anniversary of (official) programming errors) Greg 'groggy' Lehey
2021-06-19 15:48               ` 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
2021-06-16  8:16 [TUHS] 70th anniversary of (official) programming errors Jason Stevens

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=20210618210047.5uogF%steffen@sdaoden.eu \
    --to=steffen@sdaoden.eu \
    --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).