News for hackers. Stuff that matters.
Re:Google+ names policy discriminates against American Nativ... by raverbashing on Saturday March 08, 2014 @10:10AM (#7365367)
"It's satire"

Absolutely not!

Case sensitivity varies amongst countries.

One very simple occidental example: in France names are usually written LASTNAME Firstname

So if you type Lastname and your DB doesn't normalize the capitalization of names you won't match

So for the last name the search is case insensitive but for the first name not so much.

Another example is Turkish, where there are two capital I's, one with a dot, one without.

And not alphabets have a notion of case.

Re:Google+ names policy discriminates against American Nativ... by abrowne on Saturday March 08, 2014 @12:28PM (#7365719)
> Another example is Turkish, where there are two capital I's, one with a dot, one without.

It's even more complicated: they have two letter Is, one with a dot in both lower and uppercase (İ/i) and one dotless (I/ı) in both cases. So any automatic case change needs to take this into account or the letter will get switched. This also make using fonts with fi ligatures problematic.

http://en.wikipedia.org/wiki/Dotless_I

Re:Google+ names policy discriminates against American Nativ... by lstamour on Saturday March 08, 2014 @01:52PM (#7365950)
This is also why quite a few programs have bugs when running on Turkish phones if they use locale-default case changes. Always specify a US English locale if you need to send along a certain code in uppercase, or process other inputs in ASCII. Internationalisation is tough. My favourite part is when systems don't allow last names with "special characters" including spaces, hyphens and periods.
Re:Google+ names policy discriminates against American Nativ... by rmc on Sunday March 09, 2014 @07:50AM (#7368197)
And even normalizaing capitalization of names isn't always simple. How do you correctly capitalize "mcgee"? "Mcgee" or "McGee"?