>
> KCodings are obsolete and should be completely removed. So I don’t think
> this needs to be fixed.
>
Sweet - that works for me :).
Have you had a chance to take a look at my other commit (regarding issue
#4946)?
-Charles
On Tue, Aug 31, 2010 at 8:28 PM, Tomas Matousek <
tomas.matou...@micro
KCodings are obsolete and should be completely removed. So I don't think this
needs to be fixed.
Besides Encoding.UTF8 is not a UTF8 singleton. You can create multiple
different UTF8Encoding instances. We should compare encoding CodePage but on
Silverlight that property is not availabl, so we n
