Bill Medland wrote:
Does anyone know of any problems with the cp1252 encoding,
especially with trashing memory.
My program (much too big to post) works fine when I use
System.Text.Encoding.GetEncoding(65000), 65001 or 20127.
However if I use 1252, even though I am quite sure all the
characters are in the range 0 to 127 I start getting
out-of-scope variables changed.
Is this a known issue?
Kind of yes, but it should be fixed. At least I can't say
if your code should work fine since I don't know what you have ;-)
I've fixed several encoding bugs before, but haven't merged all
of them since I had been waiting for the bug reporter about
the exact expected behavior. Maybe it's time to ignore it and
just port all of them.
Atsushi Eno
_______________________________________________
Mono-list maillist - [email protected]
http://lists.ximian.com/mailman/listinfo/mono-list
