<?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 for Decompiled</title>
	<atom:link href="http://www.edwardstafford.com/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.edwardstafford.com/blog</link>
	<description>Code, Rants, Raves, Reviews and Mutterings from the IT trenches.</description>
	<pubDate>Sat, 22 Nov 2008 21:28:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>Comment on Zone Alarm Plus Microsoft Update Prevents Internet Access by Ed Stafford</title>
		<link>http://www.edwardstafford.com/blog/2008/07/10/zone-alarm-plus-microsoft-update-prevents-internet-access/#comment-1789</link>
		<dc:creator>Ed Stafford</dc:creator>
		<pubDate>Sun, 13 Jul 2008 04:18:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.edwardstafford.com/blog/?p=34#comment-1789</guid>
		<description>Thanks! Nice to know I was able to help someone out.</description>
		<content:encoded><![CDATA[<p>Thanks! Nice to know I was able to help someone out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Zone Alarm Plus Microsoft Update Prevents Internet Access by needed protection</title>
		<link>http://www.edwardstafford.com/blog/2008/07/10/zone-alarm-plus-microsoft-update-prevents-internet-access/#comment-1788</link>
		<dc:creator>needed protection</dc:creator>
		<pubDate>Fri, 11 Jul 2008 21:48:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.edwardstafford.com/blog/?p=34#comment-1788</guid>
		<description>thanks this helped</description>
		<content:encoded><![CDATA[<p>thanks this helped</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on HTML Email vs Plain Text Email. by Ed Stafford</title>
		<link>http://www.edwardstafford.com/blog/2008/03/14/html-email-vs-plain-text-email/#comment-804</link>
		<dc:creator>Ed Stafford</dc:creator>
		<pubDate>Wed, 02 Apr 2008 20:20:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.edwardstafford.com/blog/2008/03/14/html-email-vs-plain-text-email/#comment-804</guid>
		<description>Andrea,
Thanks for your input. You make some good arguments especially with the mobile devices. "Elegantly-degrading methods"! - I am adding that to my wish list. Your right that, in the end, it should be up to the recipient of our messages to decide how they want to receive and read the email. In order to reach more devices and give readers more options, then I guess it's a no brainer.</description>
		<content:encoded><![CDATA[<p>Andrea,<br />
Thanks for your input. You make some good arguments especially with the mobile devices. &#8220;Elegantly-degrading methods&#8221;! - I am adding that to my wish list. Your right that, in the end, it should be up to the recipient of our messages to decide how they want to receive and read the email. In order to reach more devices and give readers more options, then I guess it&#8217;s a no brainer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on HTML Email vs Plain Text Email. by Ed Stafford</title>
		<link>http://www.edwardstafford.com/blog/2008/03/14/html-email-vs-plain-text-email/#comment-803</link>
		<dc:creator>Ed Stafford</dc:creator>
		<pubDate>Wed, 02 Apr 2008 20:04:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.edwardstafford.com/blog/2008/03/14/html-email-vs-plain-text-email/#comment-803</guid>
		<description>Subhankar,
Thanks for your feedback. Part of my frustration with sending email is that you can't control the how the message is rendered on the other end. I think plain text formats provide better support with fewer issues, but that could just as well be an easy way out. I think what you are describing is called Multi-part alternative. I think that adding the multi-part alternative headers and support to our lists is probably the best option. Good luck with your PHP mailer.</description>
		<content:encoded><![CDATA[<p>Subhankar,<br />
Thanks for your feedback. Part of my frustration with sending email is that you can&#8217;t control the how the message is rendered on the other end. I think plain text formats provide better support with fewer issues, but that could just as well be an easy way out. I think what you are describing is called Multi-part alternative. I think that adding the multi-part alternative headers and support to our lists is probably the best option. Good luck with your PHP mailer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on HTML Email vs Plain Text Email. by Andrea</title>
		<link>http://www.edwardstafford.com/blog/2008/03/14/html-email-vs-plain-text-email/#comment-801</link>
		<dc:creator>Andrea</dc:creator>
		<pubDate>Wed, 02 Apr 2008 12:24:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.edwardstafford.com/blog/2008/03/14/html-email-vs-plain-text-email/#comment-801</guid>
		<description>I think both types of mailings have value, since it gives users the options to choose their preference depending on whether or not their more visually oriented vs. text oriented in their reading.  Not to mention that, depending on what email options you have -- web-based company email vs. the option to use a mail client vs. reading email on a mobile device -- it's nice to be able to pick and choose what works for you.

I'm more likely to subscribe to an email list or email updates if I have the option to switch to plain text, mostly because so many HTML mailings are coded really poorly even for a mail client, and I can't usually see that until I receive the first one.  I also tend to read email on my Blackberry a good deal, and fishing through the unrendered code for the text of the message it thoroughly unfun.  If only mailers used elegantly-degrading methods...</description>
		<content:encoded><![CDATA[<p>I think both types of mailings have value, since it gives users the options to choose their preference depending on whether or not their more visually oriented vs. text oriented in their reading.  Not to mention that, depending on what email options you have &#8212; web-based company email vs. the option to use a mail client vs. reading email on a mobile device &#8212; it&#8217;s nice to be able to pick and choose what works for you.</p>
<p>I&#8217;m more likely to subscribe to an email list or email updates if I have the option to switch to plain text, mostly because so many HTML mailings are coded really poorly even for a mail client, and I can&#8217;t usually see that until I receive the first one.  I also tend to read email on my Blackberry a good deal, and fishing through the unrendered code for the text of the message it thoroughly unfun.  If only mailers used elegantly-degrading methods&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on HTML Email vs Plain Text Email. by Subhankar Ray</title>
		<link>http://www.edwardstafford.com/blog/2008/03/14/html-email-vs-plain-text-email/#comment-799</link>
		<dc:creator>Subhankar Ray</dc:creator>
		<pubDate>Wed, 02 Apr 2008 00:24:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.edwardstafford.com/blog/2008/03/14/html-email-vs-plain-text-email/#comment-799</guid>
		<description>It happened to be the same issue bothering me a lot recently. My php mailer does mess up my text email [at least my test shows] extra lines, wrong line breaks. They do not look pretty at all. Today I got an email from Google, look very much like a text message, however, looking in to the source shows it is a html email with bare minimum tags for better formatting. In the worst case, html email must show the text part [if I understand it right]. Hence, I am going to use html email very soon. For the problem of deliverability, I added domain key and SPF.</description>
		<content:encoded><![CDATA[<p>It happened to be the same issue bothering me a lot recently. My php mailer does mess up my text email [at least my test shows] extra lines, wrong line breaks. They do not look pretty at all. Today I got an email from Google, look very much like a text message, however, looking in to the source shows it is a html email with bare minimum tags for better formatting. In the worst case, html email must show the text part [if I understand it right]. Hence, I am going to use html email very soon. For the problem of deliverability, I added domain key and SPF.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on HTML Email vs Plain Text Email. by Michael</title>
		<link>http://www.edwardstafford.com/blog/2008/03/14/html-email-vs-plain-text-email/#comment-778</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Fri, 14 Mar 2008 21:03:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.edwardstafford.com/blog/2008/03/14/html-email-vs-plain-text-email/#comment-778</guid>
		<description>While I personally prefer text email, I think that HTML email definitely has a place when you're doing broadcast mailings - but only if you're doing it through a service like MyEmma.  The cost is more than worth it, you get to put out beautiful emails that won't be triggered by spam filters.</description>
		<content:encoded><![CDATA[<p>While I personally prefer text email, I think that HTML email definitely has a place when you&#8217;re doing broadcast mailings - but only if you&#8217;re doing it through a service like MyEmma.  The cost is more than worth it, you get to put out beautiful emails that won&#8217;t be triggered by spam filters.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How Twitter has changed my life by Social Media Breakfast 5: How Twitter is changing our lives</title>
		<link>http://www.edwardstafford.com/blog/2008/02/14/26/#comment-727</link>
		<dc:creator>Social Media Breakfast 5: How Twitter is changing our lives</dc:creator>
		<pubDate>Thu, 14 Feb 2008 22:05:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.edwardstafford.com/blog/2008/02/14/26/#comment-727</guid>
		<description>[...] Ed Stafford: How Twitter has changed my life [...]</description>
		<content:encoded><![CDATA[<p>[...] Ed Stafford: How Twitter has changed my life [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Installing LinuxMCE 1.1 Beta 2 - The Good, The Bad, and The (mostly) Ugly! by Ed Stafford</title>
		<link>http://www.edwardstafford.com/blog/2007/06/04/installing-linuxmce-11-beta-2-the-good-the-bad-and-the-mostly-ugly/#comment-542</link>
		<dc:creator>Ed Stafford</dc:creator>
		<pubDate>Tue, 01 Jan 2008 23:49:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.edwardstafford.com/blog/?p=12#comment-542</guid>
		<description>@M Swamynathan
Honestly, I'm not sure what is causing your problem. There could possibly be an issue with the sources.list used by apt, or a bad cd burn. You could try downloading the ISO images directly to you Kubuntu desktop before you start the lmce install and instruct the installer to use those (ISOs) instead of the CDs. That worked for me.

I'd also suggest you visit the LinuxMCE forums and post your question there. There are many people willing to help you out with LMCE issues. Some of them are very knowledgeable with the product.</description>
		<content:encoded><![CDATA[<p>@M Swamynathan<br />
Honestly, I&#8217;m not sure what is causing your problem. There could possibly be an issue with the sources.list used by apt, or a bad cd burn. You could try downloading the ISO images directly to you Kubuntu desktop before you start the lmce install and instruct the installer to use those (ISOs) instead of the CDs. That worked for me.</p>
<p>I&#8217;d also suggest you visit the LinuxMCE forums and post your question there. There are many people willing to help you out with LMCE issues. Some of them are very knowledgeable with the product.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Installing LinuxMCE 1.1 Beta 2 - The Good, The Bad, and The (mostly) Ugly! by M Swamynathan</title>
		<link>http://www.edwardstafford.com/blog/2007/06/04/installing-linuxmce-11-beta-2-the-good-the-bad-and-the-mostly-ugly/#comment-539</link>
		<dc:creator>M Swamynathan</dc:creator>
		<pubDate>Tue, 01 Jan 2008 04:40:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.edwardstafford.com/blog/?p=12#comment-539</guid>
		<description>Hi Stafford,

I am trying to install the Linux MCE... The Kubuntu is successfully installed, after i install the LinuxMCE installer, then i finish the CD 1 and CD 2, then the system need the Kubuntu live cd... it takes the more time and i will get the konsole screen ( scrolling commands and texts), then suddenly, mysql installation failed- broken pipe msg will appeared. Then Installation failed msg will be showed.

how can i rectify this bug.

Thanks in advance</description>
		<content:encoded><![CDATA[<p>Hi Stafford,</p>
<p>I am trying to install the Linux MCE&#8230; The Kubuntu is successfully installed, after i install the LinuxMCE installer, then i finish the CD 1 and CD 2, then the system need the Kubuntu live cd&#8230; it takes the more time and i will get the konsole screen ( scrolling commands and texts), then suddenly, mysql installation failed- broken pipe msg will appeared. Then Installation failed msg will be showed.</p>
<p>how can i rectify this bug.</p>
<p>Thanks in advance</p>
]]></content:encoded>
	</item>
</channel>
</rss>
