![]() ![]() To be technical, neither UTF-8 nor UTF-16 is "Unicode" - both are merely external encodings meant for the exchange of data - actual "Unicode characters" are 32 bits. ![]() but it turned out I was years late, and UTF-8 won out: it is way more complete, has amazing levels of compatibility with older code, etc. I actually fell victim to this same thing about 3 years ago, when I thought I would be all correct and cool etc by re-writing my Windows apps to use the Microsoft version of UTF-16. To be clear, these are the label strings supplied by HWiNFO for the sensors in the shared memory segment. Now what I see with the BETA is the sequence "ef bf bd" - which is used for illegal characters.Īnd yes, as you suspect, I am using the Windows "beta" feature of "Use Unicode UTF-8 for worldwide language support" - with the underlying locale set to "English (United States)". As a detail, this trace was produced using OutputDebugStringA - which works great with UTF-8. where the "degrees" symbol was properly encoded in UTF-8 as "c2 b0". RxTRACE> HWIM|GIGABYTE Z690 AORUS MASTER (ITE IT8689E)|VRM MOS ☌ RxTRACE> HWIM|GIGABYTE Z690 AORUS MASTER (ITE IT8689E)|PCIEX16 ☌ RxTRACE> HWIM|GIGABYTE Z690 AORUS MASTER (ITE IT8689E)|CPU ☌ RxTRACE> HWIM|GIGABYTE Z690 AORUS MASTER (ITE IT8689E)|PCH ☌ RxTRACE> HWIM|GIGABYTE Z690 AORUS MASTER (ITE IT8689E)|System1 ☌ So, until this BETA, HWiNFO was putting out this (for example): Actually, I don't even think Microsoft any longer recommends you use their version of UTF-16, as UTF-16 (any version) doesn't have nearly the range of characters that can be encoded as does UTF-8. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |