<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Please, no HTML!</title>
	<atom:link href="http://universitydiary.wordpress.com/2008/12/01/please-no-html/feed/" rel="self" type="application/rss+xml" />
	<link>http://universitydiary.wordpress.com/2008/12/01/please-no-html/</link>
	<description></description>
	<lastBuildDate>Mon, 16 Nov 2009 14:35:41 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ultan</title>
		<link>http://universitydiary.wordpress.com/2008/12/01/please-no-html/#comment-678</link>
		<dc:creator>Ultan</dc:creator>
		<pubDate>Mon, 01 Dec 2008 13:28:35 +0000</pubDate>
		<guid isPermaLink="false">http://universitydiary.wordpress.com/?p=442#comment-678</guid>
		<description>ASCII characters won&#039;t give you maximum compatability in terms of communication at all, but exclude most people from communicating in their native language.

However, I&#039;m not a fan of HTML formatted emails either - they&#039;re annoying, the formatting adds no value, and it can also play havoc for users with visual disabilities.  That said, we are moving towards a scenario of richer user experiences, way beyond HTML capability.  Furthermore, some HTML syntax  - for links  - is definitely preferable in e-mail instead of attaching huge files to the e-mail when they should really be referenced on a server.

From a user experience viewpoint your device should render the text the way you want it, if it can&#039;t,  then maybe  it&#039;s the *device* that&#039;s being pedantic.  You can&#039;t expect senders to know....</description>
		<content:encoded><![CDATA[<p>ASCII characters won&#8217;t give you maximum compatability in terms of communication at all, but exclude most people from communicating in their native language.</p>
<p>However, I&#8217;m not a fan of HTML formatted emails either &#8211; they&#8217;re annoying, the formatting adds no value, and it can also play havoc for users with visual disabilities.  That said, we are moving towards a scenario of richer user experiences, way beyond HTML capability.  Furthermore, some HTML syntax  &#8211; for links  &#8211; is definitely preferable in e-mail instead of attaching huge files to the e-mail when they should really be referenced on a server.</p>
<p>From a user experience viewpoint your device should render the text the way you want it, if it can&#8217;t,  then maybe  it&#8217;s the *device* that&#8217;s being pedantic.  You can&#8217;t expect senders to know&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Ruane</title>
		<link>http://universitydiary.wordpress.com/2008/12/01/please-no-html/#comment-677</link>
		<dc:creator>Jason Ruane</dc:creator>
		<pubDate>Mon, 01 Dec 2008 10:04:19 +0000</pubDate>
		<guid isPermaLink="false">http://universitydiary.wordpress.com/?p=442#comment-677</guid>
		<description>I didn&#039;t even like it when the world moved from monospace or  fixed-width font systems. I preferred it when sending a mail from a fixed width system, such as a VAX terminal would probably arrive in a similar machine at the destination. There was a subtle comfort in its simplicity; lowly whitespace characters could be used for things akin to comedic timing in speech.
I guess I am the arche-TYPE-al fan of Courier 10, appreciative of ASCII art and bandwidth efficiency.
http://en.wikipedia.org/wiki/ASCII_art</description>
		<content:encoded><![CDATA[<p>I didn&#8217;t even like it when the world moved from monospace or  fixed-width font systems. I preferred it when sending a mail from a fixed width system, such as a VAX terminal would probably arrive in a similar machine at the destination. There was a subtle comfort in its simplicity; lowly whitespace characters could be used for things akin to comedic timing in speech.<br />
I guess I am the arche-TYPE-al fan of Courier 10, appreciative of ASCII art and bandwidth efficiency.<br />
<a href="http://en.wikipedia.org/wiki/ASCII_art" rel="nofollow">http://en.wikipedia.org/wiki/ASCII_art</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Mahler</title>
		<link>http://universitydiary.wordpress.com/2008/12/01/please-no-html/#comment-676</link>
		<dc:creator>Scott Mahler</dc:creator>
		<pubDate>Mon, 01 Dec 2008 02:29:36 +0000</pubDate>
		<guid isPermaLink="false">http://universitydiary.wordpress.com/?p=442#comment-676</guid>
		<description>As a computer programming myself, I have to agree with you. While I appreciate the attempt at originality, there are many potential problems, especially when you consider the fact that most of these people don&#039;t really know what they are doing.</description>
		<content:encoded><![CDATA[<p>As a computer programming myself, I have to agree with you. While I appreciate the attempt at originality, there are many potential problems, especially when you consider the fact that most of these people don&#8217;t really know what they are doing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
