Thanks to the comment to the question by Afzaal, I realized that you probably mean obsolete encoding Windows 1252:
https://en.wikipedia.org/wiki/Windows-1252[
^].
And 182=0xb6 is the "pilcrow sign" ('¶') in both "ANSI" and Unicode; and 131=0x83 is "no break here" in Unicode and undefined in what is usually referred to as "ANSI".
Here we are coming to a delicate point. "ANSI", as a character set, is not something certain. This "term" may refer to different things. Please read about it:
https://en.wikipedia.org/wiki/ANSI_character_set[
^].
At the same time, the term "ANSI" for the character was extensively used as Windows-specific jargon word in pre-Unicode Windows versions, and later renamed as a term using for legacy non-Unicode Windows character encodings supported by modern versions of Windows for backup compatibility, to certain extent. See the reference above and the references article and MSDN documentation.
I have to note that Windows is full of confusing jargon words not meeting any standard. Even the term "Unicode" is routinely used in jargon sense, as the encoding UTF-16LE, which is the internal encoding use for representing Unicode characters/strings in memory, which provides no justification to call it "Unicode". Other UTFs are called by their standard names, but rarely mentioning endianness.In contrast to that, .NET is fully based on Unicode standard which is also the main standard for XML (which supports many character sets), and hence WPF and everything else. You should understand that Unicode is not encoding. Unicode encodings are standardized as UTFs which support the same
character repertoire, without any exclusions; and XML
character entities have nothing to do with UTFs, they directly specify Unicode
character points.
Conclusion: You need to get rid of the obsolete encoding and transcode everything in Unicode, and only to Unicode. In .NET, it can be done using the class
System.Text.Encoding
(its use is pretty obvious from MSDN documentation):
https://msdn.microsoft.com/en-us/library/system.text.encoding%28v=vs.110%29.aspx[
^].
—SA