Wenn nun bei dieser Kodierung ein Zeichen gefunden wird, welches nicht im Unicode abgebildet werden kann, so erhält dieses Zeichen den Wert EF BF BD – besagter Replacement Character. Damit ist dann auch erklärt warum die binären Dateien hauptsächlich nur noch aus diesen Zeichen bestanden. Die echten Daten wurden beim Kopiervorgang ...
Hex and octal UTF-8 byte input should have the bytes separated by spaces. "UTF-8 bytes as Latin-1 characters" is what you typically see when you display a UTF-8 file with a terminal or editor that only knows about 8-bit characters. Spaces are ignored in the input of bytes as Latin-1 characters, to make it easier to cut-and-paste from dump output.
ef bc 86: fullwidth ampersand: u+ff07 ' ef bc 87: fullwidth apostrophe: u+ff08 ( ef bc 88: fullwidth left parenthesis: u+ff09 ) ef bc 89: fullwidth right parenthesis: u+ff0a * ef bc 8a: fullwidth asterisk: u+ff0b + ef bc 8b: fullwidth plus sign: u+ff0c, ef bc 8c: fullwidth comma: u+ff0d - ef bc 8d: fullwidth hyphen-minus: u+ff0e ...
It appears that there has been some Microsoft auto-update that has occurred within this month (November 2007) that has caused a .NET 2.0 application that I wrote (using C#) to convert A0 to EF BF BD when running the following code: Previous to Nov 3, 2007 this application did not convert A0 and all was well. A0 happens to be a   in ISO 8859-1.