http://blogs.msdn.com/michkap/archive/2005/02/11/371010.aspxIf you look at the description of the Ordinal sort in the CompareOptions enumeration in the .NET Framework, it seems pretty clear: Indicates that the string comparison must be done using the Unicode values of each character, which is a fast comparisonen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/michkap/archive/2005/02/11/371010.aspx#371026Fri, 11 Feb 2005 14:31:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:371026Serge WautierIt could have been worse: A rough WORD sort breaking the surrogate pairs ! <br>http://blogs.msdn.com/michkap/archive/2005/02/11/371010.aspx#372132Mon, 14 Feb 2005 10:17:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:372132Dmitry Jemerov's WeblogIt looks like a recent post in Michael Kaplan&amp;rsquo;s blog, where he demonstrates usage of surrogate pairs, exposes a bug in the implementation of System.IO.BinaryReader.ReadString() in&amp;nbsp;.NET 1.1. The bug appears in Omea as ArgumentException &amp;ldquo;Conversion buffer overflow&amp;rdquo; when trying to...http://blogs.msdn.com/michkap/archive/2005/02/11/371010.aspx#372134Mon, 14 Feb 2005 07:19:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:372134Dmitry JemerovLooks like you found a third bug by your blogging... <br><a target="_new" href="http://blogs.jetbrains.com/yole/archives/000035.html">http://blogs.jetbrains.com/yole/archives/000035.html</a> <br> <br>If it's really a bug in .NET BCL, could you please send it to the appropriate place?http://blogs.msdn.com/michkap/archive/2005/02/11/371010.aspx#372135Mon, 14 Feb 2005 07:24:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:372135Michael KaplanWhat I reported was not a bug (well, maybe a doc bug!). <br> <br>What you report is a different issue, and if true it definitely sounds like bug -- I will forward it on. :-)