5 ms·

Sorry to be a pedant, but: I was confused for a moment about what this article was about due to the casing of the title, "An open Google now is about to...", wh

Sorry to be a pedant, but: I was confused for a moment about what this article was about due to the casing of the title, "An open Google now is about to...", which sounds like Google is becoming "open" and is "now about to..." do something. I wondered, "what about Google being 'open' is going to make Android smart?" The problem starts on Wired's end, where the title was title-cased in the HTML title, and upper-cased for the in-body header, leaving no trace of the original intended casing, "An open Google Now is about to...". And then when the article was submitted to Hacker News, where we traditionally sentence-case things, the submitter had to do the sentence-casing themselves and overlooked this finer point. Alas, for if only CSS text-transforms could just magically make title- and sentence-casing work...

deleted 12y ago
[deleted]
frivoal 12y ago
title casing (and sentence casing) is one of these problems that is easy for humans to perform on a case by case basis, but hard to solve in an automated and generic way. Not only is it language dependent (and any solution baked into css needs to work for all languages where it is relevant), and do various publishers have slightly differing rules about it, but it also depends on the meaning, as this example shows. Whether "Now" is part of the "Google Now" name, or works as an adverb influences the casing. CSS has become quite a bit more complicated these days, but it is still quite far form being sentient. TL;DR: Proper title casing is AI-complete
mmahemoff 12y ago
Mods: Please s/now/Now the title
morganvachon 12y ago
For me, the title initially read as Google Now being open sourced, and I was eager to read about such a bold but strange move on Google's part. As soon as I started reading the article and realized it was about opening up the API, I lost all interest. I mean, I do get how good it is that they are opening up the API for third parties, but I was really hoping to read about Google turning around from their recent anti-open-source/anti-open-platform moves and back towards embracing open source again. Oh well.
pjc50 12y ago
Google Now is the winter of our discontent.

deleted 12y ago

[deleted]

frivoal 12y ago

title casing (and sentence casing) is one of these problems that is easy for humans to perform on a case by case basis, but hard to solve in an automated and generic way. Not only is it language dependent (and any solution baked into css needs to work for all languages where it is relevant), and do various publishers have slightly differing rules about it, but it also depends on the meaning, as this example shows. Whether "Now" is part of the "Google Now" name, or works as an adverb influences the casing. CSS has become quite a bit more complicated these days, but it is still quite far form being sentient. TL;DR: Proper title casing is AI-complete

mmahemoff 12y ago

Mods: Please s/now/Now the title

morganvachon 12y ago

For me, the title initially read as Google Now being open sourced, and I was eager to read about such a bold but strange move on Google's part. As soon as I started reading the article and realized it was about opening up the API, I lost all interest. I mean, I do get how good it is that they are opening up the API for third parties, but I was really hoping to read about Google turning around from their recent anti-open-source/anti-open-platform moves and back towards embracing open source again. Oh well.

pjc50 12y ago

Google Now is the winter of our discontent.