News for hackers. Stuff that matters.

A comment on Glibc Buffer Overflow in Iconv. Parent comment

Re:Glibc Buffer Overflow in Iconv by bdd8f1df777b on Sunday April 21, 2024 @07:49AM (#40104936)
I've seldom seen UTF16 text file even under Windows. Sometimes, but not that often.
[ Parent | on HN ]
Re:Glibc Buffer Overflow in Iconv by Tempest1981 on Sunday April 21, 2024 @10:45AM (#40106141)
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

[ Parent | on HN ]
Re:Glibc Buffer Overflow in Iconv by frutiger on Sunday April 21, 2024 @02:03PM (#40107797)
You need to translate any text content into UTF-16 before calling Win32 APIs in most cases.
[ Parent | on HN ]
Re:Glibc Buffer Overflow in Iconv by Mindless2112 on Sunday April 21, 2024 @02:54PM (#40108198)
You can set the code page to UTF-8 now.

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

[ Parent | on HN ]
Re:Glibc Buffer Overflow in Iconv by bdd8f1df777b on Sunday April 21, 2024 @10:53PM (#40111077)
But if you are calling Win32 APIs, you can call Win32 APIs MultiByteToWideChar/WideCharToMultiByte to convert between UTF8 and UTF16. No need for iconv.
[ Parent | on HN ]
Re:Glibc Buffer Overflow in Iconv by frutiger on Monday April 22, 2024 @09:34AM (#40114201)
That’s right. I was just replying to parents poster that it’s not about text files.
[ Parent | on HN ]