<?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:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: Doesn&#8217;t anyone QA these days?</title>
	<atom:link href="http://blog.flashgen.com/2007/09/15/doesnt-anyone-qa-these-days/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.flashgen.com/2007/09/15/doesnt-anyone-qa-these-days/</link>
	<description>An infrequent look at developments in the world of the Flash Platform by Mike Jones - Flash Platform Consultant</description>
	<lastBuildDate>Sun, 07 Mar 2010 21:04:34 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John Dowdell</title>
		<link>http://blog.flashgen.com/2007/09/15/doesnt-anyone-qa-these-days/comment-page-1/#comment-93120</link>
		<dc:creator>John Dowdell</dc:creator>
		<pubDate>Sat, 15 Sep 2007 16:07:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.flashgen.com/2007/09/15/doesnt-anyone-qa-these-days/#comment-93120</guid>
		<description>I wish each page on the website had a feedback route, myself. But if there were such a thing, then the following info could help the owner try to see the problem too: page; format (HTML? PDF?);  browser (brand/OS/version); and printer info. (The site owner would know the first two, but we in weblogs don&#039;t.)

If you could drop off a piece of paper with the above info when you attend the conference, then the staff at the front desk could ferry it to the page owner, reducing the chance we&#039;d see such a problem again, thanks.

jd/adobe</description>
		<content:encoded><![CDATA[<p>I wish each page on the website had a feedback route, myself. But if there were such a thing, then the following info could help the owner try to see the problem too: page; format (HTML? PDF?);  browser (brand/OS/version); and printer info. (The site owner would know the first two, but we in weblogs don&#8217;t.)</p>
<p>If you could drop off a piece of paper with the above info when you attend the conference, then the staff at the front desk could ferry it to the page owner, reducing the chance we&#8217;d see such a problem again, thanks.</p>
<p>jd/adobe</p>
]]></content:encoded>
	</item>
</channel>
</rss>
