by Michael S. Kaplan, published on 2006/11/24 01:46 -05:00, original URI: http://blogs.msdn.com/b/michkap/archive/2006/11/23/1136924.aspx
Bart asks in the Suggestion Box:
Why does WideCharToMultiByte(CP_ACP,
accept 0x0081 and turns it into 0x81 even though the acp is cp1252 and 0x81 is not defined ?
These tables could be thought of as more of an idealized notion of the code pages, perhaps? :-)
The more accurate and latest tables are actually posted up on the Unicode site, the Cross Mapping Tables link to the various vendors like Microsoft, like the "Best Fit" tables of of this page.
The 1252 "WindowsBestFit" table there has the entry in question (just as Windows has had it, for quite some time).
About the only real benefit to such a mapping even existing is that it will allow a C1 Unicode control character to roundtrip. Dubious benefit, to be sure, but too late to change at this point....
This post brought to you by U+0081, a C1 control character
go to newer or older post, or back to index or month or day