Sorting it all Out Michael Kaplan's random stuff of dubious value Be sure to read the disclaimer here first!
Richard asked in the Suggestion Box, and I decided to dispatch quickly:
Why is it that English (en-US, because there is no en-GB) Windows and .NET don't know how to upper case a Latin Small Latter Sharp S even with the de-DE locale specified: "\u00DF".ToUpper(CultureInfo.GetCultureInfo("de-DE")) does not return "SS", but "ß"? The Unicode casing file CaseFolding.txt has 00DF; F; 0073 0073; # LATIN SMALL LETTER SHARP S Is this a Window's limitation? (Which would not help, given I'm trying to put together a demo of doing the right thing to build I18n into an application update.)
This is a question I have talked about many times in the past, as a simple search for U+00df indicates. And most importantly, since Casing and IgnoreCase are still not the same thing and Collation != Case (a.k.a. Collation <> Case), for now this is how casing will work on Microsoft platforms -- what Unicode refers to as simple casing....
This post sponsored by "ß" (U+00df, LATIN SMALL LETTER SHARP S)
At the beginning of the week I posted Part 0 of this series, so I figured I should start the series at
There are several scripts that have the notion of case, like Latin, Cyrillic, Greek, Armenian, Coptic,
That night I saw in the pipeline fair A character that wasn't there Non-existence won't stop the encoding;
SQL Server likes to keep a bit of independence from the operating system. At the same time, they like
I am writing this blog from my own laptop waiting in the ER at the hospital (all of the quotes are from