<pun> we're all being so insensitive to other cultures here! </pun>
in a nutshell - if your current language settings has a character that is not the exact same value as one of the invariant characters which are all 'generic'..ex 0 1 2 3 4 5 6 7 8 9 % & * ( ) - _ = + ' " ; : . > "," < ? / a b c d e f g h i j k l m n o p q r s t u v w x y z A B C D E F G H I J K L M N O P Q R S T U V W X Y Z and anything you call uses invariant - a character substitution will occur. I think this quote from ms is appropriate: "However, you should use the invariant culture only for processes that require culture-independent results, such as system services. In other cases, it produces results that might be linguistically incorrect or culturally inappropriate." lets not be culturally inappropriate either. On Mon, Sep 8, 2008 at 11:19 AM, Per Bolmstedt <[EMAIL PROTECTED] > wrote: > On Mon, 8 Sep 2008 13:23:16 -0400, =?ISO-8859-1?Q?S=E9bastien_Lorion?= > <[EMAIL PROTECTED]> wrote: > > > by using OrdinalIgnoreCase, you are limiting yourself to only the > > first 128 chars of ASCII, which in 2008 is kinda out of fashion... > > How so? > > According to "New Recommendations for Using Strings in Microsoft .NET 2.0 > "[1]; "Comparisons made using OrdinalIgnoreCase are behaviorally the > composition of two calls: calling ToUpperInvariant on both string > arguments, and doing an Ordinal comparison.". > > 1: http://msdn.microsoft.com/en-us/library/ms973919.aspx > > =================================== > This list is hosted by DevelopMentor(R) http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com > =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
