4 ms·
There is no need for a libaray, there is just need for a consistent standard. Meaning, if all programms would use UTF-8, fine. But they don't. But character -
by hutzlibu 6y ago
There is no need for a libaray, there is just need for a consistent standard.
Meaning, if all programms would use UTF-8, fine. But they don't.
But character -encoding is somewhat complicated, because there are a lot of languages out there. Some who even need more than 2 bytes per character, so you get special cases, which break on another system etc.
- z3t4 6y agoMost programs use something that is compatible with UTF-8. And UTF-8 is also backwards compatible with ASCII which is why A-z usually works. I actually think UTF-16 is the most common. The issues start to arise when three or more code points/bytes are combined into one character/glyph.
- moksly 6y agoBeing in the public sector, doing our 3rd party integration and being from Denmark gets me the joy of having to deal with a lot of relatively different APIs of very varied quality and æøå in names. Sometimes when people think they are using UTF-8, they aren’t. I’m not sure if that’s because they are incompetent or if their tooling lies to them, but I’ve gone through soooooo many weird encodings over the years trying to match what was specified as standard UTF-8.