Hacker News new | past | comments | ask | show | jobs | submit
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.

loading story #50557070
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?