Why is StringBuilder changing pipes to "o" umlaut when loading a pipe-delimited string?

[Ray Stevens]

I am loading a pipe-delimited string from a DataSet into StringBuilder, such
as 00P|23423||98723 (etc.). For some reason the pipe character is displaying
in the debugger as "o" with two small dots on top (i.e., with an umlaut). Is
StringBuilder modifying my pipe character and, if so, how do I stop it?

 

[Basti Wiesner]

I am loading a pipe-delimited string from a DataSet into StringBuilder, such

as 00P|23423||98723 (etc.). For some reason the pipe character is displaying
in the debugger as "o" with two small dots on top (i.e., with an umlaut). Is
StringBuilder modifying my pipe character and, if so, how do I stop it?

Seems that the Debugger is just using another encoding für displaying strings.
..NET stores string as Unicode. Maybe the debugger does not.

Normally StringBuilder doesn't modify any characters.

Basti

 

[James Curran]

I cannot possibly accept the idea that VS's debugger does not understand
Unicode.
I also cannot accept the idea that there's a font which replaces "|"
(ASCII Standard 0x7C for the last 40 years) with character "ö" (nonstandard,
generally accepted as 0xF6 and/or 0x99 for about the last 15 years)

Now, what could be happening is that instead of the proper pipe
character (0x7C), you may be using the "broken bar" character (nonstandard,
but normally, 0xA6), and that may be an umlauted o in some fonts.


--
--
Truth,
James Curran
[erstwhile VC++ MVP]

Home: www.noveltheory.com Work: www.njtheater.com
Blog: www.honestillusion.com Day Job: www.partsearch.com