<?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: Searchify: Calendar entry</title>
	<atom:link href="http://olilan.co.uk/searchify-calendar-entry/feed/" rel="self" type="application/rss+xml" />
	<link>http://olilan.co.uk/searchify-calendar-entry/</link>
	<description>home of Searchify and Touch Calendar</description>
	<lastBuildDate>Mon, 28 Nov 2011 07:15:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Sebastian</title>
		<link>http://olilan.co.uk/searchify-calendar-entry/comment-page-1/#comment-892</link>
		<dc:creator>Sebastian</dc:creator>
		<pubDate>Sat, 25 Dec 2010 08:33:12 +0000</pubDate>
		<guid isPermaLink="false">http://olilan.co.uk/?p=46#comment-892</guid>
		<description>&lt;blockquote cite=&quot;#commentbody-718&quot;&gt;
&lt;strong&gt;&lt;a href=&quot;#comment-718&quot; rel=&quot;nofollow&quot;&gt;acebone&lt;/a&gt; :&lt;/strong&gt;
Small point:
This syntax: 
15/3 0900 interview
Will produce an entry in the current year.
IMHO it would be more clever if it would produce an entry on the next upcoming 15/3 (no matter if it is this year or next year). After all – when you need to do a quick calendar entry it’s 99% sure that your appointment is in the future and not in the past.
&lt;/blockquote&gt;

totally agreed!</description>
		<content:encoded><![CDATA[<blockquote cite="#commentbody-718"><p>
<strong><a href="#comment-718" rel="nofollow">acebone</a> :</strong><br />
Small point:<br />
This syntax:<br />
15/3 0900 interview<br />
Will produce an entry in the current year.<br />
IMHO it would be more clever if it would produce an entry on the next upcoming 15/3 (no matter if it is this year or next year). After all – when you need to do a quick calendar entry it’s 99% sure that your appointment is in the future and not in the past.
</p></blockquote>
<p>totally agreed!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: acebone</title>
		<link>http://olilan.co.uk/searchify-calendar-entry/comment-page-1/#comment-718</link>
		<dc:creator>acebone</dc:creator>
		<pubDate>Tue, 26 Oct 2010 12:14:57 +0000</pubDate>
		<guid isPermaLink="false">http://olilan.co.uk/?p=46#comment-718</guid>
		<description>Absolutely brilliant!!

I saw someone saying that their search was slowed down by searchify, well not here (HTC Desire)

Small point:

This syntax: 

15/3 0900 interview

Will produce an entry in the current year.

IMHO it would be more clever if it would produce an entry on the next upcoming 15/3 (no matter if it is this year or next year). After all - when you need to do a quick calendar entry it&#039;s 99% sure that your appointment is in the future and not in the past.</description>
		<content:encoded><![CDATA[<p>Absolutely brilliant!!</p>
<p>I saw someone saying that their search was slowed down by searchify, well not here (HTC Desire)</p>
<p>Small point:</p>
<p>This syntax: </p>
<p>15/3 0900 interview</p>
<p>Will produce an entry in the current year.</p>
<p>IMHO it would be more clever if it would produce an entry on the next upcoming 15/3 (no matter if it is this year or next year). After all &#8211; when you need to do a quick calendar entry it&#8217;s 99% sure that your appointment is in the future and not in the past.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

