Unicode in Microsoft Windows: Difference between revisions

Content deleted Content added
Windows 11 warning, regarding at least the new start menu, a hint to how implemetned (do not see it for corresponding page for Win10): "Make sure your LayoutModification.json uses UTF-8 encoding."
rm Unix supremacist biased source
Tags: Reverted references removed
Line 33:
 
=== Programming platforms ===
Microsoft's compilers often fail at producing UTF-8 string constants from UTF-8 source files. The most reliable method is to turn ''off'' UNICODE, ''not'' mark the input file as being UTF-8 (i.e. do not use a [[UTF-8#Byte order mark|BOM]]), and arrange the string constants to have the UTF-8 bytes. If a BOM was added, a Microsoft compiler will interpret the strings as UTF-8, convert them to UTF-16, then convert them ''back'' into the current locale, thus destroying the UTF-8., as C and C++ <refcode>[http:char<//utf8everywhere.org/#faq.literalcode> UTF-8type Everywherewas FAQ:not Howmeant doto I writebe UTF-8 string literal in my C++ code?]</ref>. Without a BOM and using a single-byte locale, Microsoft compilers will leave the bytes in a quoted string unchanged.
 
== See also ==