When I first read it it seemed to me that if I'm comparing strings in a text
editor I need not be concerned about culture because I'm only interested in
equality or not equal. That's true isn't it? If I'm doing case sensitive
comparisons it seems to me the bit are just compared and are either equal or
not.
However, it occurred to me that I don't know how RegEx does case insensitive
comparisons. Does it convert to upper or lower and if it does, does that
make culture important since again, we are just looking for equality.
Thanks
PS
I read the site you suggested and also
Culture-Insensitive String Operations.
But it just makes suggestions about when to use or not use
culture-insensitive string operations. I can't imagine what a
culture-insensitive operation does unless there are some fixed rules that
are applied with out regard to the culture in effect.
If that's the case is "mailto".ToUpper <"MAILTO" case insensitive equal
even in Turkey?
"Steve Gerrard" <my********@comcast.netwrote in message
news:05******************************@comcast.com. ..
AAaron123 wrote:
>I'm trying to understand CultureInvariant as it applies to Regex.
I'd appreciate seeing a string that will be matched by another string
when CultureInvariant is set and not matched when it is not set.
Or the reverse.
I get many Goggle hits but the all assume the reader knows about
Culture.
I need to get oriented.
Thanks
Start with this link at MSDN, titled Comparing and Sorting Data for a
Specific Culture:
http://msdn2.microsoft.com/en-us/lib...0c(VS.80).aspx
An example of a culture sensitive issue:
"mailto".ToUpper <"MAILTO"
- if you are in Turkey. ;-)
