<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Google autocomplete now fixes spelling problems</title>
	<atom:link href="http://www.malcolmcoles.co.uk/blog/autocomplete-fixing-spelling/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.malcolmcoles.co.uk/blog/autocomplete-fixing-spelling/</link>
	<description>Where to find Malcolm Coles, reviews, and tips on how to do things I couldn&#039;t do.</description>
	<lastBuildDate>Mon, 25 Mar 2013 16:22:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Nichola Stott</title>
		<link>http://www.malcolmcoles.co.uk/blog/autocomplete-fixing-spelling/#comment-7322</link>
		<dc:creator>Nichola Stott</dc:creator>
		<pubDate>Mon, 18 Jan 2010 10:59:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.malcolmcoles.co.uk/blog/?p=3853#comment-7322</guid>
		<description>I agree this is a clear usability improvement on the query input side; though it would be nice if there was different handling of my request according to the selection method. E.g. if I start to type &quot;wether&quot; (male goat/sheep) and select &quot;wether&quot; from the auto-complete options - we could maybe infer I&#039;m less likely to be interested in BBC Weather in position 1, as I have made a comparative selection - kind of pre-qualified my intent? Maybe this is on the cards and maybe all of these recent shennanigans are part of a CTR data collection exercise?</description>
		<content:encoded><![CDATA[<p>I agree this is a clear usability improvement on the query input side; though it would be nice if there was different handling of my request according to the selection method. E.g. if I start to type "wether" (male goat/sheep) and select "wether" from the auto-complete options - we could maybe infer I'm less likely to be interested in BBC Weather in position 1, as I have made a comparative selection - kind of pre-qualified my intent? Maybe this is on the cards and maybe all of these recent shennanigans are part of a CTR data collection exercise?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Malcolm Coles</title>
		<link>http://www.malcolmcoles.co.uk/blog/autocomplete-fixing-spelling/#comment-7319</link>
		<dc:creator>Malcolm Coles</dc:creator>
		<pubDate>Mon, 18 Jan 2010 10:25:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.malcolmcoles.co.uk/blog/?p=3853#comment-7319</guid>
		<description>It handles stationary / stationery well too - giving a mix of terms relating to both spellings if you type in stationary (as opposed to just returning stationery results if you do search on stationary).

The stationery/stationary thing makes me wonder if it&#039;s CTR plus next search data. Presumably in the old days, people would search for stationary, see things that didn&#039;t move and then search again for stationery when they realised it was a mis-spelling (possibly prompted by a &quot;did you mean&quot;).</description>
		<content:encoded><![CDATA[<p>It handles stationary / stationery well too - giving a mix of terms relating to both spellings if you type in stationary (as opposed to just returning stationery results if you do search on stationary).</p>
<p>The stationery/stationary thing makes me wonder if it's CTR plus next search data. Presumably in the old days, people would search for stationary, see things that didn't move and then search again for stationery when they realised it was a mis-spelling (possibly prompted by a "did you mean").</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joanna Butler</title>
		<link>http://www.malcolmcoles.co.uk/blog/autocomplete-fixing-spelling/#comment-7317</link>
		<dc:creator>Joanna Butler</dc:creator>
		<pubDate>Mon, 18 Jan 2010 09:40:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.malcolmcoles.co.uk/blog/?p=3853#comment-7317</guid>
		<description>Agreed - much better user experience. Actually useful in most cases. It seems fine with US/UK spellings (e.g. favourite/favorite, colour/color, humor/humour) but why not acknowledge optimisation? Odd... If it&#039;s based on search volume then we should also be pushed &#039;humor&#039; over &#039;humour&#039;. But we aren&#039;t. I&#039;m guessing CTR based.</description>
		<content:encoded><![CDATA[<p>Agreed - much better user experience. Actually useful in most cases. It seems fine with US/UK spellings (e.g. favourite/favorite, colour/color, humor/humour) but why not acknowledge optimisation? Odd... If it's based on search volume then we should also be pushed 'humor' over 'humour'. But we aren't. I'm guessing CTR based.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
