Various locale mismatch scenarios in Windows clipboard text format synthesis
29 points by ibobev
by jey
0 subcomment
> When I ran this program, I expected the `CF_OEMTEXT` string to have the byte 44, but it didn’t. It had the byte 90. We will start unraveling this mystery next time.
Whoa there exists something Raymond Chen didn’t know about Windows core APIs?
by akersten
4 subcomments
i don't know what it would take to remove all this OEM LCID 1252 ANSI nonsense from computing (well, just Windows) but if I were in charge of "make sure developers ever willingly choose to work on Win32 instead of any other sane Unicode only platform" I would make it my top priority
whatever imagined problem is solved by marking clipboard text with some magical locale indicator is surely not as important as being able to interop literally just unicode characters between programs without having to read a 2-part blog post
Hacker News