You need to translate any text content into UTF-16 before calling Win32 APIs in most cases.

You can set the code page to UTF-8 now.

https://learn.microsoft.com/en-us/windows/apps/design/global...

But if you are calling Win32 APIs, you can call Win32 APIs MultiByteToWideChar/WideCharToMultiByte to convert between UTF8 and UTF16. No need for iconv.

That’s right. I was just replying to parents poster that it’s not about text files.

iirc, RC files are often UTF-16

https://stackoverflow.com/questions/72143553

> it looks like switching back to UTF-16 would unblock your experience with Resource Editor

Edit: reportedly changed in VS2017 15.9