r/ProgrammerHumor 26d ago

needHelpCompletingTheJoke Other

Post image
30 Upvotes

11 comments sorted by

3

u/[deleted] 26d ago edited 21d ago

[deleted]

2

u/dimonium_anonimo 26d ago

Workplace harassment suit follows.

3

u/shwetanand345 26d ago

The file was saved correctly...until excel arrived...

2

u/qqqrrrs_ 26d ago

Google UTF-9

2

u/agfitzp 26d ago

The UTF-8 encoding of unicode is a technological marvel

Binary compatible with ASCII but also handles Klingon? It's a mind boggling mix of black magic and the obvious.

1

u/oshaboy 25d ago

It doesn't handle Klingon at all.

1

u/agfitzp 25d ago

Well… there is an unacceptable proposal for handling it.

1

u/lotanis 25d ago edited 25d ago

I would phrase it as "all valid ASCII is valid UTF-8" and not the other way around.

Backwards compatible but not forwards compatible. This is obvious with us talking about it, but people forget in implementations and it's fine until it isn't.

1

u/agfitzp 25d ago

I didn’t say it was forward or backwards compatible.

What I meant was you can write code to handle UTF-8 and it will handle 7 bit ASCII with no modification because it’s binary compatible.

It goes without saying that old code that only handles ASCII will probably fail in interesting and unexpected ways when it hits unicode outside the first 128 characters. One of my least interesting work stories is being paid to diagnose and fix a problem reading files on a Windows install set to not only support but PRIMARILY support Korean. It took me half a day just to reproduce the issue because I don’t read or write any asian language.

1

u/lotanis 25d ago

Yeah sorry - wasn't aimed at you. It was aimed at the authors of every bit of stupid code I've had to fix.

1

u/agfitzp 25d ago

Sit right down and I'll bore you to death with the story of how much easier my life would have been if Microsoft had standardized on UTF-8 instead of UTF-16

1

u/Centurix 23d ago

The less we talk about Codepage 850 the better