4 ms·
Technically it's had support since (IIRC) Windows 7. What this does is call the translation functions for you instead of having to do it yourself.
by ChrisSD 6y ago
Technically it's had support since (IIRC) Windows 7. What this does is call the translation functions for you instead of having to do it yourself.
- huhtenberg 6y agoConversion functions - MultiByteToWideChar & co. - were in since Windows 2000 and the UTF8 codepage was supported as early as XP if not in W2K as well.
- ChrisSD 6y agoAh thanks! It's funny because I can't recall ever using code page 65001 before 7. Maybe there was a reason for that or maybe I simply didn't know it existed until then. Or maybe I thought it simpler to just use UTF-16. I can't remember.
- gpvos 6y agoIt existed in W2K and maybe even earlier, but there were bugs in the console regarding codepage 65001, so you couldn't use it as the default. This was not fixed yet in XP, maybe in 7 though.