Atara,
I am looking for a site that will include information about
specification of languages that might cause other bugs.
Are they bugs? Did you contact MS directly to verify they are bugs?
I would contact Microsoft directly if I suspected an alleged bug in the
framework that did not allow me to compare "i" to "I"!
Are you aware of such a site?
In addition to the links below try asking this "down the hall" in the
microsoft.public.dotnet.internationalization newsgroup I suspect will offer
you a plethora of more sites!
Note: I would strongly discourage your code to "workaround" this problem as
you may actually be introducing new problems for other cultures!
I would make sure that I was using the "correct" compare method. In addition
to the "=" operator, there is String.Compare & String.CompareOridinal with
overloads. I would make sure I had a good understanding (or at least good
enough) of cultures & how strings worked in the various cultures.
For example:
Imports System.Globalization
' This is effectively what "string1.ToUpper() = string2.ToUpper()" does:
If String.Compare(string1, string2, True, CultureInfo.CurrentCulture) =
0 Then
' This is effectively what you loop is trying to do:
If String.Compare(string1, string2, True, CultureInfo.InvariantCulture)
= 0 Then
For details on compare strings see:
http://msdn.microsoft.com/library/d...e/html/cpconsortingdataforspecificculture.asp
http://msdn.microsoft.com/library/d.../cpconculture-insensitivestringoperations.asp
Interesting enough this page talks about your "bug"!
http://msdn.microsoft.com/library/d.../html/cpconcustomcasemappingssortingrules.asp
http://msdn.microsoft.com/library/d...ormingculture-insensitivestringoperations.asp
Plus any sub topics of the above...
Hope this helps
Jay