I'm not sure what you expect :) You've found consistent behavior, and it matches the behavior documented in http://www.unicode.org/Public/MAPPINGS/VENDORS/MICSFT/WindowsBestFit/bestfit1252.txt
IANA http://www.iana.org/assignments/charset-reg/windows-1252 points to both the non-best fit "standard" mapping and he best fit mapping. -Shawn From: Buck Golemon [mailto:[email protected]] Sent: Friday, December 7, 2012 3:03 PM To: unicode; Shawn Steele Subject: Re: data for cp1252 One week: bump. On Wed, Nov 28, 2012 at 10:52 AM, Buck Golemon <[email protected]<mailto:[email protected]>> wrote: Shawn, can I get your comments? Does this seem irrelevant? On Mon, Nov 26, 2012 at 5:05 PM, Buck Golemon <[email protected]<mailto:[email protected]>> wrote: I've compiled cross-browser data on the question of how to cp1252 decodes the byte 0x81. http://bukzor.github.com/encodings/cp1252.html In summary, all browsers agree that it decodes to U+81. Opera initially thought it was undefined, but changed their mind in version 12 (the current version).
