Unicode in Microsoft Windows: Difference between revisions

Content deleted Content added
+
Various encoding schemes: rm paradoxically, having one function to convert from the platform's standard representation to other encodings is perfectly reasonable
Line 17:
 
== Various encoding schemes ==
Although Windows used the UTF-16LE encoding scheme internally, in [[NTFS]] file system, in [[Portable Executable|executables]] and sometimes in [[text files]], Unicode's [[byte oriented]] encodings [[UTF-8]] and even [[UTF-7]] are supported as well. An application which has to support UTF-8 or UTF-7 by the means of [[Windows API]] should, paradoxically, call the same functions [[MultiByteToWideChar]] and WideCharToMultiByte used to support "legacy" (i.e. pre-Unicode) code pages.<ref>{{cite web |url=http://stackoverflow.com/questions/166503/utf-8-in-windows |title=UTF-8 in Windows |publisher=[[Stack Overflow]] |accessdate=July 1, 2011}}</ref> Many applications imminently have to support UTF-8 because it is the most used of Unicode encoding schemes in various [[network protocol]]s, including the [[Internet Protocol Suite]].
 
<references />