<?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 for Prefix Technologies Blog</title>
	<atom:link href="http://blog.prefix.co.za/?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://blog.prefix.co.za</link>
	<description>Next Generation Web Application Thinking!</description>
	<pubDate>Thu, 09 Sep 2010 07:53:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on How to install Trac on Windows by alsotop</title>
		<link>http://blog.prefix.co.za/?p=32&#038;cpage=1#comment-169</link>
		<dc:creator>alsotop</dc:creator>
		<pubDate>Mon, 22 Jun 2009 11:03:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.prefix.co.za/2008/05/06/how-to-install-trac-on-windows-running-apache/#comment-169</guid>
		<description>Hi, Thanks for the advice. But yeah, I needed to make sure setuptools was installed before I installed Trac, otherwise it would complain that pkg_resources was not available.</description>
		<content:encoded><![CDATA[<p>Hi, Thanks for the advice. But yeah, I needed to make sure setuptools was installed before I installed Trac, otherwise it would complain that pkg_resources was not available.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How to install Trac on Windows by keith</title>
		<link>http://blog.prefix.co.za/?p=32&#038;cpage=1#comment-140</link>
		<dc:creator>keith</dc:creator>
		<pubDate>Mon, 06 Oct 2008 07:53:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.prefix.co.za/2008/05/06/how-to-install-trac-on-windows-running-apache/#comment-140</guid>
		<description>I'm glad it helped. I'll check out the Setuptools requirement again and amend the post if required.</description>
		<content:encoded><![CDATA[<p>I&#8217;m glad it helped. I&#8217;ll check out the Setuptools requirement again and amend the post if required.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How to install Trac on Windows by Umeku</title>
		<link>http://blog.prefix.co.za/?p=32&#038;cpage=1#comment-139</link>
		<dc:creator>Umeku</dc:creator>
		<pubDate>Sun, 05 Oct 2008 18:06:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.prefix.co.za/2008/05/06/how-to-install-trac-on-windows-running-apache/#comment-139</guid>
		<description>Thanks for the info! I was struggling with Trac installation under Windows and this post solved it.

p.s. I did have to install Setuptools for it to work.</description>
		<content:encoded><![CDATA[<p>Thanks for the info! I was struggling with Trac installation under Windows and this post solved it.</p>
<p>p.s. I did have to install Setuptools for it to work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Advice: How to design emails for Outlook 2007 by Josh Adler</title>
		<link>http://blog.prefix.co.za/?p=12&#038;cpage=1#comment-4</link>
		<dc:creator>Josh Adler</dc:creator>
		<pubDate>Thu, 11 Oct 2007 05:24:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.prefix.co.za/2007/09/30/advice-how-to-design-emails-for-outlook-2007/#comment-4</guid>
		<description>Thanks for the reply Aatish. 

I will be the first to acknowledge that the new Office presents great and powerful features and opportutnies. But it is a little difficult for us to ensure that the almost 2m people who recieve email from pMailer on a monthly basis all install a plugin to view  more css-driven mailers.

The gripe is that in order to deliver Office 2007 compliant email, those who don't use Office 2007 and could have received a richer experience via mail from marketers, will now be unable to.


We'll have to work around it. Nothing new, and I'm sure we'll still be able to deliver rich and well-designed mailers going forward as Office 2007 begins to penetrate the market further.

Josh</description>
		<content:encoded><![CDATA[<p>Thanks for the reply Aatish. </p>
<p>I will be the first to acknowledge that the new Office presents great and powerful features and opportutnies. But it is a little difficult for us to ensure that the almost 2m people who recieve email from pMailer on a monthly basis all install a plugin to view  more css-driven mailers.</p>
<p>The gripe is that in order to deliver Office 2007 compliant email, those who don&#8217;t use Office 2007 and could have received a richer experience via mail from marketers, will now be unable to.</p>
<p>We&#8217;ll have to work around it. Nothing new, and I&#8217;m sure we&#8217;ll still be able to deliver rich and well-designed mailers going forward as Office 2007 begins to penetrate the market further.</p>
<p>Josh</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Advice: How to design emails for Outlook 2007 by aatishr</title>
		<link>http://blog.prefix.co.za/?p=12&#038;cpage=1#comment-3</link>
		<dc:creator>aatishr</dc:creator>
		<pubDate>Sun, 07 Oct 2007 17:47:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.prefix.co.za/2007/09/30/advice-how-to-design-emails-for-outlook-2007/#comment-3</guid>
		<description>Hello Prefix. I like the new look - good, friendly colour shceme.

I'd like to delve a little further into this email rendering issue. 

After a chat with Josh (Prefix), and some questions from my own customers and partners, I've been looking into this and have some information to share.

First, a little background. In Office 2003, Microsoft used the Word HTML rendering engine to create and edit emails in Outlook, but, confusingly, used Internet Explorer's engine to display emails.This was quite frustrating to designers, as their emails looked different at the receiving end. Obviously, the solution was to use the same engine for editing and viewing.

I don't pretend to know the reasons for Microsoft's choice of the Word engine over Internet Explorer's (which I believe is clearly superior from a web-standards point of view). I can only speculate.

There are ways around this, although certainly not as easy as ticking a checkbox in a menu dialog.

The ability to modify and enhance functionality in the Office 2007 system is vastly improved over previous releases. Creating custom forms, or custom form regions in Outlook is the most relevant feature here.

It's possible to build an Outlook add-in that replaces the current form inspector (the bit that decodes and displays an email - e.g. the Outlook reading pane) with a custom one. This is fairly easy to do in VS2008, as it's mostly wizard driven. This custom inspector would have the IE7 browser on it's surface (this is available as a control in Visual Studio 2008 - shipping March 2008), and would display the email in all it's standards-compliant glory.

I actually stumbled upon a code sample that did this (will post it as soon as I find it again). Something like this could be cooked up in a day and sent to people on the receiving end. With ClickOnce deployment (another new Office add-in feature that's available in VS2008), an end user could install this with a minimum of fuss, and spend the rest of the day basking in the CSS goodness of  pMailer.

Based on the relative simplicity of such a solution, I'm sure that Microsoft will soon release something like it. I'll let you know if we do.

I apologise for the length of this post, but I hope that you found it helpful.

Aatish</description>
		<content:encoded><![CDATA[<p>Hello Prefix. I like the new look - good, friendly colour shceme.</p>
<p>I&#8217;d like to delve a little further into this email rendering issue. </p>
<p>After a chat with Josh (Prefix), and some questions from my own customers and partners, I&#8217;ve been looking into this and have some information to share.</p>
<p>First, a little background. In Office 2003, Microsoft used the Word HTML rendering engine to create and edit emails in Outlook, but, confusingly, used Internet Explorer&#8217;s engine to display emails.This was quite frustrating to designers, as their emails looked different at the receiving end. Obviously, the solution was to use the same engine for editing and viewing.</p>
<p>I don&#8217;t pretend to know the reasons for Microsoft&#8217;s choice of the Word engine over Internet Explorer&#8217;s (which I believe is clearly superior from a web-standards point of view). I can only speculate.</p>
<p>There are ways around this, although certainly not as easy as ticking a checkbox in a menu dialog.</p>
<p>The ability to modify and enhance functionality in the Office 2007 system is vastly improved over previous releases. Creating custom forms, or custom form regions in Outlook is the most relevant feature here.</p>
<p>It&#8217;s possible to build an Outlook add-in that replaces the current form inspector (the bit that decodes and displays an email - e.g. the Outlook reading pane) with a custom one. This is fairly easy to do in VS2008, as it&#8217;s mostly wizard driven. This custom inspector would have the IE7 browser on it&#8217;s surface (this is available as a control in Visual Studio 2008 - shipping March 2008), and would display the email in all it&#8217;s standards-compliant glory.</p>
<p>I actually stumbled upon a code sample that did this (will post it as soon as I find it again). Something like this could be cooked up in a day and sent to people on the receiving end. With ClickOnce deployment (another new Office add-in feature that&#8217;s available in VS2008), an end user could install this with a minimum of fuss, and spend the rest of the day basking in the CSS goodness of  pMailer.</p>
<p>Based on the relative simplicity of such a solution, I&#8217;m sure that Microsoft will soon release something like it. I&#8217;ll let you know if we do.</p>
<p>I apologise for the length of this post, but I hope that you found it helpful.</p>
<p>Aatish</p>
]]></content:encoded>
	</item>
</channel>
</rss>
