No need to throw out the baby with the streamwriter; they probably could have just put in a replacementhttp://blogs.msdn.com/b/michkap/archive/2008/11/13/9065138.aspxSo anyway, Kim 's other recent blog, entitled Making a StreamWriter usable even after given garbage characters , highlights an interesting difference some of the methodology between the way that Windows and .Net handle encoding and codepages. In Windowsen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)re: No need to throw out the baby with the streamwriter; they probably could have just put in a replacementhttp://blogs.msdn.com/b/michkap/archive/2008/11/13/9065138.aspx#9102391Sun, 16 Nov 2008 03:27:47 GMT91d46819-8472-40ad-a661-2c78acb4018c:9102391Michael S. Kaplan<p>Well, you and I could occasionally collaborate on titles. :-)</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9102391" width="1" height="1">re: No need to throw out the baby with the streamwriter; they probably could have just put in a replacementhttp://blogs.msdn.com/b/michkap/archive/2008/11/13/9065138.aspx#9094421Sat, 15 Nov 2008 13:12:41 GMT91d46819-8472-40ad-a661-2c78acb4018c:9094421MSDNArchive<p>btw, I wish I'd thought of that title. Right after posting I was actually lamenting my lack of &quot;title flair&quot;</p><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9094421" width="1" height="1">re: No need to throw out the baby with the streamwriter; they probably could have just put in a replacementhttp://blogs.msdn.com/b/michkap/archive/2008/11/13/9065138.aspx#9094400Sat, 15 Nov 2008 13:11:06 GMT91d46819-8472-40ad-a661-2c78acb4018c:9094400MSDNArchive<p>Excellent! But you've set a dangerous precedent...I may start adding &quot;todo: Michael&quot; notes when I'd rather hand off Unicode explanations to the official Unicode bulldog!</p><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9094400" width="1" height="1">