From: Angelo Papenhoff <aap@papnet.eu>
To: 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 20:19:58 +0200 [thread overview]
Message-ID: <ZIynzm5XSBKGgWcR@indra.papnet.eu> (raw)
In-Reply-To: <alpine.DEB.2.21.2306161350310.30495@sd-119843.dedibox.fr>
On 16/06/23, Steve Nickolas wrote:
> 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.
There are two origins of this character. One ſs and one ſʒ.
You can see it here:
https://upload.wikimedia.org/wikipedia/commons/0/0e/Sz_modern.svg
1 and 2 are ſs, 3 and 4 are ſʒ
Now it gets even more off-topic (sorry):
My personal favourite (and the one I've adopted in my handwriting) is
the one used in Berlin street signs, obviously ſʒ:
https://upload.wikimedia.org/wikipedia/commons/3/32/Strasse-FF-Cst-Berlin.png
Interestingly I've noticed the Bonn street signs look rather similar, maybe
it's a thing capitals do.
aap
next prev parent reply other threads:[~2023-06-16 18:20 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
2023-06-16 18:19 ` Angelo Papenhoff [this message]
[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=ZIynzm5XSBKGgWcR@indra.papnet.eu \
--to=aap@papnet.eu \
--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).