Hacker News new | past | comments | ask | show | jobs | submit
It’s not. There are multiple uppercase forms, including “SS”, “SZ”, and the uppercase ß character, all of which are well-established, which makes all of them correct according to the principle of linguistic descriptivism.
And according to linguistic perscriptivism, the upper case of ß is ẞ since 2017. (SS is also allowed, but no longer preferred)
The uppercase ß was introduced as an option in 2017 but only became the preferred option in 2024.

Interestingly Unicode included the uppercase ß since 2008.

tbh I'm German and just learned about this now. I don't even know which keyboard incantation I would have to use to create this abomination. My android keyboard does not seem to have an uppercase ß.

> tbh I'm German and just learned about this now.

It's a little amusing how many Germans I've heard this from, meanwhile as a non-German I think I first heard about ß and ẞ at least a decade ago.

Maybe this is one of those "outsiders have fresh eyes" things where googling "wait, wtf is up with ß" is not something most Germans would do?

A similar thing happens with Japanese natives and ヷ/わ゛ -- most are not aware this character existed historically and they usually also incorrectly guess how it's read.

But according to the "principle" of blindly following the Unicode standard with no tailoring, the "correct" form is SS. (And Unicode's stability guarantees preclude ever changing it to ẞ)
>And Unicode's stability guarantees preclude ever changing it to ẞ

This seems like a bad property for a system that encodes human writing systems.

Human writing systems themselves have that very same property. The stability of written language prevents them to adapt swiftly to changes to spoken language.

Knight / night is an example for English. That k should be gone, right? Or all those silent -ment and e in French.

Enter the computer and I'm not surprised that German speakers end up mostly with SS because that's what computers do when automatically upcasing words.

A lot of spelling changes are dictated by what's available on keyboards. In Italian we accept E' as È because we don't have that upper case character on our keyboard. Automatic uppercase on start of sentences fixed it where it's available and mobile keywords show an È as an option of you long press a shifted e. But what if you are writing Italian in an English locale form field with a hardware keyboard (here with an OS with English locale) or you have to write È in the middle of a sentence or, go back 30 or 40 years, you have to use a typing machine?

I'm am sure that every language that had to go through a phase of adapting to ASCII and to the limits on the layout of keyboards has similar stories to tell.

The writing systems don't have that property, because you can write slang and spell words differently all fine. Orthography might have that property, but that's in the nature of orthography.
The stability guarantee precludes changing the default conversion, but not adding a new 'de-DE-2024' locale with updated rules, similar to the existing '1901' and '1996' locales.
What stops you from blindly following the standard with tailoring?
Compatibility concerns, which can quickly become security concerns.
are those worse than an existing security bug?