From: Steve Nickolas <usotsuki@buric.co>
To: John Cowan <cowan@ccil.org>
Cc: groff@gnu.org, TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: end-S/long-S (was: Re: GNU eqn clarifications and reforms)
Date: Fri, 16 Jun 2023 13:51:18 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.21.2306161350310.30495@sd-119843.dedibox.fr> (raw)
In-Reply-To: <CAD2gp_RDkmZG+MroGuRPpvGj+pxnziv54jw+bf2Tfo8gXX=zVw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 833 bytes --]
On Fri, 16 Jun 2023, John Cowan wrote:
> On Fri, Jun 16, 2023 at 12:18 PM Paul Winalski <paul.winalski@gmail.com>
> wrote:
>
>
>> German also has a ligature letter called eszet that is a fusion of a
>> long s (the one that resembles the English letter f) and a short s.
>>
>
> Not a short s, but a z, as the name indicates: es-zett, S-Z. This
> reflects the use of z in Old and Middle High German to represent a sibilant
> sound distinct from s, derived from /t/ by the High German sound shift but
> distinct from original /s/. When the distinction was lost in the 13C, z
> came to be used for its modern sound /ts/, but the ligature came to
> represent the merged /s/.
I've seen ß used in some copies of the Geneva Bible with exactly the
modern German sense, as a ligature of long s and normal s.
-uso.
next prev parent reply other threads:[~2023-06-16 17:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 2:18 [TUHS] Re: GNU eqn clarifications and reforms Douglas McIlroy
2023-06-16 3:20 ` G. Branden Robinson
[not found] ` <37ea7f2b-e8f7-3cfe-a27d-ece47c5dc0f7@esi.com.au>
2023-06-16 5:07 ` G. Branden Robinson
2023-06-16 7:43 ` [TUHS] Re: end-S/long-S (was: Re: GNU eqn clarifications and reforms) markus schnalke
2023-06-16 9:39 ` Wesley Parish
2023-06-16 16:18 ` Paul Winalski
2023-06-16 17:46 ` John Cowan
2023-06-16 17:51 ` Steve Nickolas [this message]
2023-06-16 18:19 ` Angelo Papenhoff
[not found] ` <1da83cf3-7fac-b5fd-dec-e4b4313d3a@esi.com.au>
2023-06-16 19:38 ` [TUHS] Re: GNU eqn clarifications and reforms G. Branden Robinson
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=alpine.DEB.2.21.2306161350310.30495@sd-119843.dedibox.fr \
--to=usotsuki@buric.co \
--cc=cowan@ccil.org \
--cc=groff@gnu.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).