Can this really not be fixed?
I still see this in various text that’s meant to be readable.
Usually ampersands are the biggest culprit, but is it just a really sacred data type that can’t be upgraded to include punctuation, but can include the foreign looking wingdings that try to stand in for it?
I’m just confused on why those characters have multi character reference names that aren’t part of the regular alphabet or punctuation set either, but those still show up instead of having room to just remove the erroneous reference with the actual character.
It’s 2026, just dig out this fossil and fix it already.




Exactly. My point is to move to a single universal standard that is used by literally everything so this never happens. Just cut off everything that can’t be updated, and it can just sink or swim based on how well it can parse the new table.
Fuck all that ancient non-updateable shit. There’s no good reason that old table still exists, much less be possible to use this side of 2000.
Obviously this has legacy problems, but fuck those systems, everyone gotta get new shit now, tough shit. The old table should be cause for new shit to fail compiling in the first place. Shouldn’t be possible to use it.
Let’s just make forward progress, and lose the chains.