The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Winalski <paul.winalski@gmail.com>
To: markus schnalke <meillo@marmaro.de>
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 12:18:29 -0400	[thread overview]
Message-ID: <CABH=_VSaJ=FtEzHdvcZmC1p3snXo8dBsP1817J5QOvsFig7VYw@mail.gmail.com> (raw)
In-Reply-To: <1qA46y-3OI-00@marmaro.de>

On 6/16/23, markus schnalke <meillo@marmaro.de> wrote:
>
> [2023-06-16 07:07] "G. Branden Robinson" <g.branden.robinson@gmail.com>
>>
>> For inſtance, the United States uſed to employ a non-final lowercaſe S
>> in the founding documents of its preſent government, where you can see
>> exhibits of the "Congreſs of the United States".
>
> In old German, up to WWII, namely in Fraktur (the printed letters)
> and Sütterlin (the handwritten letters) both kinds of S are
> present.
>
> Today, the long-S has only survived in some old company and
> restaurant names, many of them changing by and by to the end-S,
> because younger Germans can't read long-S and don't understand it
> anymore.

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.
It is used when a 's' sound is immediately preceded by a long vowel or
a diphthong and not followed by a consonant.  When the glyph for eszet
isn't available 'ss' is substituted, as in the word 'strasse'
(street).

-Paul W.

  parent reply	other threads:[~2023-06-16 16:18 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 [this message]
2023-06-16 17:46           ` John Cowan
2023-06-16 17:51             ` Steve Nickolas
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='CABH=_VSaJ=FtEzHdvcZmC1p3snXo8dBsP1817J5QOvsFig7VYw@mail.gmail.com' \
    --to=paul.winalski@gmail.com \
    --cc=groff@gnu.org \
    --cc=meillo@marmaro.de \
    --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).