<?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"
	>
<channel>
	<title>Comments on: Microsoft Outlook 2007 really hates commas</title>
	<atom:link href="http://blog.sugarenia.com/archives/rantings/microsoft-outlook-2007-really-hates-commas/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.sugarenia.com/archives/rantings/microsoft-outlook-2007-really-hates-commas</link>
	<description>As Sweet As Bitter</description>
	<pubDate>Sat, 22 Nov 2008 10:37:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Sugar</title>
		<link>http://blog.sugarenia.com/archives/rantings/microsoft-outlook-2007-really-hates-commas#comment-50735</link>
		<dc:creator>Sugar</dc:creator>
		<pubDate>Fri, 23 Nov 2007 18:51:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sugarenia.com/archives/rantings/microsoft-outlook-2007-really-hates-commas#comment-50735</guid>
		<description>@KCorax: Outlook mainly locks up because of the Exchange server hoolabaloo, I guess. One thing they got right though, Outlook can be a real productivity boost, given the right circumstances.</description>
		<content:encoded><![CDATA[<p>@KCorax: Outlook mainly locks up because of the Exchange server hoolabaloo, I guess. One thing they got right though, Outlook can be a real productivity boost, given the right circumstances.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KCorax</title>
		<link>http://blog.sugarenia.com/archives/rantings/microsoft-outlook-2007-really-hates-commas#comment-50207</link>
		<dc:creator>KCorax</dc:creator>
		<pubDate>Mon, 19 Nov 2007 14:15:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sugarenia.com/archives/rantings/microsoft-outlook-2007-really-hates-commas#comment-50207</guid>
		<description>Personally I fully agree, but for the sake of legacy this can't be fixed. Consider this: You mail a list with n people and look at a list of name-surname. Each time the sw examines if it should append a word and look up for it, this leads to 2^n (Worst case after simplification) lookups.

Your mailbox is petty-small. I pack 12 GBs and another 7 in archive and I'm fast. I can't guess what's wrong. If you don't need to hook up to an exchange server and need it just for offline hotmail, consider the windows live mail which doesn't try to accomodate enterprise needs in the user experience.</description>
		<content:encoded><![CDATA[<p>Personally I fully agree, but for the sake of legacy this can&#8217;t be fixed. Consider this: You mail a list with n people and look at a list of name-surname. Each time the sw examines if it should append a word and look up for it, this leads to 2^n (Worst case after simplification) lookups.</p>
<p>Your mailbox is petty-small. I pack 12 GBs and another 7 in archive and I&#8217;m fast. I can&#8217;t guess what&#8217;s wrong. If you don&#8217;t need to hook up to an exchange server and need it just for offline hotmail, consider the windows live mail which doesn&#8217;t try to accomodate enterprise needs in the user experience.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sugar</title>
		<link>http://blog.sugarenia.com/archives/rantings/microsoft-outlook-2007-really-hates-commas#comment-50196</link>
		<dc:creator>Sugar</dc:creator>
		<pubDate>Mon, 19 Nov 2007 11:54:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sugarenia.com/archives/rantings/microsoft-outlook-2007-really-hates-commas#comment-50196</guid>
		<description>@KCorax: Ok, I was exaggerating there with the "too lazy" bit, but seriously, such a behaviour should not be left in the sense of the user. 

I want my mail program to handle everything I throw at it, and the case above, too simple web addresses separated by comma, is one of the most common cases of enumerating web addresses. Why should I care that the app would see lala as a contact name? 

The whole thing creates confusion, I know I would never use the ContactSurname, ContactName scheme in there because I don't know how in god's name this would be parsed. This behaviour does not help things a lot, imho.

As for my .pst file, the whole thing, including Spam, is a 'mere' 240MB.</description>
		<content:encoded><![CDATA[<p>@KCorax: Ok, I was exaggerating there with the &#8220;too lazy&#8221; bit, but seriously, such a behaviour should not be left in the sense of the user. </p>
<p>I want my mail program to handle everything I throw at it, and the case above, too simple web addresses separated by comma, is one of the most common cases of enumerating web addresses. Why should I care that the app would see lala as a contact name? </p>
<p>The whole thing creates confusion, I know I would never use the ContactSurname, ContactName scheme in there because I don&#8217;t know how in god&#8217;s name this would be parsed. This behaviour does not help things a lot, imho.</p>
<p>As for my .pst file, the whole thing, including Spam, is a &#8216;mere&#8217; 240MB.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KCorax</title>
		<link>http://blog.sugarenia.com/archives/rantings/microsoft-outlook-2007-really-hates-commas#comment-50195</link>
		<dc:creator>KCorax</dc:creator>
		<pubDate>Mon, 19 Nov 2007 11:33:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sugarenia.com/archives/rantings/microsoft-outlook-2007-really-hates-commas#comment-50195</guid>
		<description>Normally active directory stores names as ', ' and that's how developers and users look up for 'Atzitzikaki, Sugarenia' when accessing the AD. You could write for example: "sugabage@sugarenia.com; Atzitzikaki, Sugarenia" for two users and Outlook would treat them as two different contacts. However this flexibility means that Outlook needs to know how you group these, otherwise you would end up with more than two contacts and possible disambiguations. In this case sugabage is a one result lookup, Atzitzikaki another, and you would get a question asking you which sugarenia you mean of all the known ones. Yeah I know it's complicated, but it's also not a string replacement fix.

As for the speed, when outlook 07 shipped it was a single threaded application. Well not really, but it had many thread locks which made it behave like such. This fix (which is not in autoupdate) really changes things: http://rurl.org/cf6 . Also consider moving things to archive. They are still indexed for search (manual and search folders). The goal is to keep your main pst file under 2 gigs.</description>
		<content:encoded><![CDATA[<p>Normally active directory stores names as &#8216;, &#8216; and that&#8217;s how developers and users look up for &#8216;Atzitzikaki, Sugarenia&#8217; when accessing the AD. You could write for example: &#8220;sugabage@sugarenia.com; Atzitzikaki, Sugarenia&#8221; for two users and Outlook would treat them as two different contacts. However this flexibility means that Outlook needs to know how you group these, otherwise you would end up with more than two contacts and possible disambiguations. In this case sugabage is a one result lookup, Atzitzikaki another, and you would get a question asking you which sugarenia you mean of all the known ones. Yeah I know it&#8217;s complicated, but it&#8217;s also not a string replacement fix.</p>
<p>As for the speed, when outlook 07 shipped it was a single threaded application. Well not really, but it had many thread locks which made it behave like such. This fix (which is not in autoupdate) really changes things: <a href="http://rurl.org/cf6" rel="nofollow">http://rurl.org/cf6</a> . Also consider moving things to archive. They are still indexed for search (manual and search folders). The goal is to keep your main pst file under 2 gigs.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
