You're viewing a single thread.
It's just UTF-8
It's also UTF-8 with BOM. It's also windows western 1252. Dont get me started on international date time formatting and time assumptions :(
I wish it was just UTF-8
It's also some surprise internal representation as utf-16; that's at least still in the realm of Unicode. Would also expect there's utf-32 still floating around somewhere, but I couldn't tell you where.
And is mysql still doing that thing with
utf8as a noob trap andutf8_for_real_we_mean_it_this_time_honestor whatever they called it as normal utf8?Me too. To this Day our national Electric invoice standard uses ISO-8859-15. An that's just fine until somebody feels the need to have a look with Notepad, add a random space and save the file.
Notepad then helpfully changes the encoding to UTF-16 and the whole patch errors out somewhere down the chain.
Android defaults to UTF16
All because of java
TIL I didn't realize Java used UTF16 for its internal representation. Looks like it's a bit more complicated than that after Java 9 too
You'd think things would be simple, otherwise the existence of UTF-8.
And yet for the last 17 years, every company I've been in has had some sort of horrible mess involving unicode and non-unicode and nobody either recognising the problem, or knowing how to solve it when they did recognise it ("well, the £ turns into a ? so we just replace any ? in the filename by a £").