CenturyLink installed FTTH here a few days ago. When I called Comcast to cancel, it sounded like they intended to put up a fight until I mentioned the word "gigabit." Immediately took the wind out of the poor rep's sails.
Funny, CenturyLink launched Gigabit in Seattle - 50 miles north of me, yet had people door knocking to "tell me about it, since I've probably seen the trucks". So I looked online, just to see if it was stealth. Nope.
I called, because the database online sometimes sucks. Nope.
And then the rep was "but we do have 24mbps at your address", "No, thank you, I have 150mbps with Comcast", and the rep replied, "What do you really need that much for? I'm pretty sure you don't and are just overpaying."
I didn't even bother beyond "I work from home. I need it. Thanks. Bye."
I don't have any personal hardships with the existing system, but whenever I see my statement of benefits where a doctor bills $X and insurance pays them $X/4, I always scratch my head and think, "This is normal? There has GOT to be a better way!"
I know how you feel, but my response to this guy was to want to take him, put my arm around his shoulder, congratulate him on finding a way to motivate himself as he is right now, and warn him that he's got five, maybe six decades ahead of him, every one filled with possibilities that aren't going to depend on what he does right NOW NOW NOW. There's time. Everyone always has the wherewithal to change things, to start things, to build things, and to make things better, no matter how the past went.
It's really weird that they just add special cases like that. Though I expect it's just because they don't have enough special cases yet (went from one — for the Turkish I — to two).
I'd have expected something like a generic Unicode-aware/y text management layer, and CSS text transforms would just go through that layer.
Eek. Not only are they hardcoding the logic but they mix their CSS-specific code into the function. I understand that they are handling a limited number of cases now but if I came across that kind of code in my work I'd be very sceptical.
The problem is that Unicode doesn't know about language. Unicode is just characters.
Language-aware bits are more gross, but then language often is. It's not nicely structured like most of the other things we encounter when transforming data.
> The problem is that Unicode doesn't know about language. Unicode is just characters.
I won't blame you for this, it is a common mistake, but Unicode goes far beyond merely mapping characters to integers. The Standard Annexes, Technical Reports and Technical Specifications cover pretty much all things localization from line breaking [UAX14] to regular expressions [UTS18] through date and time formatting [UTS35] or sorting [UTS10].
And as it turns out, both uppercasing and titlecasing are covered by [UAX44] as part of the SpecialCasing.txt file which provides lower, upper and title-casing (along with optional conditions) for characters with non-trivial mappings (trivial 1:1 mappings are covered in the base UnicodeData.txt file)
Yes, in Firefox the 'esszet' is transformed in SS when in capital letters. But this done since a long time. The dotted and dot-less Turkic, and the Dutch IJ, are new in Firefox 14 (which is the first browser to support it, AFAIK).
There is some specific cases with accented Greek diphthongs, where the diacritic position changes in upper and lower case, but Mozilla is working on a fix.
first diagram in the link is traffic flow. there's a blue circle going all the way around the building. appleinsider has kindly cropped out any sort of legend, i suppose it could be underground though.
