<?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: Pre-Flight, Post-Flight &amp; Automation</title>
	<atom:link href="http://tunicca-blog.com/2009/06/24/pre-flight-post-flight-automation/feed/" rel="self" type="application/rss+xml" />
	<link>http://tunicca-blog.com/2009/06/24/pre-flight-post-flight-automation/</link>
	<description>Innovating One Company at a Time</description>
	<lastBuildDate>Fri, 21 May 2010 15:02:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Halle</title>
		<link>http://tunicca-blog.com/2009/06/24/pre-flight-post-flight-automation/#comment-94</link>
		<dc:creator>Halle</dc:creator>
		<pubDate>Sun, 19 Jul 2009 03:24:39 +0000</pubDate>
		<guid isPermaLink="false">http://tunicca.wordpress.com/?p=348#comment-94</guid>
		<description>Hey this is a very interesting article! Thanks!</description>
		<content:encoded><![CDATA[<p>Hey this is a very interesting article! Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pitstop or Flightcheck? - Page 4 - PrintPlanet.com</title>
		<link>http://tunicca-blog.com/2009/06/24/pre-flight-post-flight-automation/#comment-29</link>
		<dc:creator>Pitstop or Flightcheck? - Page 4 - PrintPlanet.com</dc:creator>
		<pubDate>Thu, 02 Jul 2009 11:39:12 +0000</pubDate>
		<guid isPermaLink="false">http://tunicca.wordpress.com/?p=348#comment-29</guid>
		<description>[...]  [...]</description>
		<content:encoded><![CDATA[<p>[...]  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pre-Flight, HTML, Flash, Video, 3D?</title>
		<link>http://tunicca-blog.com/2009/06/24/pre-flight-post-flight-automation/#comment-18</link>
		<dc:creator>Pre-Flight, HTML, Flash, Video, 3D?</dc:creator>
		<pubDate>Thu, 25 Jun 2009 14:31:47 +0000</pubDate>
		<guid isPermaLink="false">http://tunicca.wordpress.com/?p=348#comment-18</guid>
		<description>[...] George from tunicca.com wrote this article about preflighting, postflighting and Automation. We invite your comments on [...]</description>
		<content:encoded><![CDATA[<p>[...] George from tunicca.com wrote this article about preflighting, postflighting and Automation. We invite your comments on [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Wilson</title>
		<link>http://tunicca-blog.com/2009/06/24/pre-flight-post-flight-automation/#comment-17</link>
		<dc:creator>Jim Wilson</dc:creator>
		<pubDate>Thu, 25 Jun 2009 12:09:00 +0000</pubDate>
		<guid isPermaLink="false">http://tunicca.wordpress.com/?p=348#comment-17</guid>
		<description>I agree with Rajesh&#039;s excellent point - if the check is for the next step, then the prefix &#039;pre&#039; is appropriate. It&#039;s still a good discussion.

Since our group rarely recieves &#039;native files&#039;, all of our checks are done at the &quot;post&quot; stage of normalized PDF, using some of the products you&#039;ve mentioned. We often find ourselves in the unpleasant position of trying to educate clients on how to perform a function they insist on performing - only to realize they aren&#039;t interested in the lesson. Like many in pre-media, we have in fact learned to make a silk purse out of a sow&#039;s ear. Or at least a reasonable approximation of one.</description>
		<content:encoded><![CDATA[<p>I agree with Rajesh&#8217;s excellent point &#8211; if the check is for the next step, then the prefix &#8216;pre&#8217; is appropriate. It&#8217;s still a good discussion.</p>
<p>Since our group rarely recieves &#8216;native files&#8217;, all of our checks are done at the &#8220;post&#8221; stage of normalized PDF, using some of the products you&#8217;ve mentioned. We often find ourselves in the unpleasant position of trying to educate clients on how to perform a function they insist on performing &#8211; only to realize they aren&#8217;t interested in the lesson. Like many in pre-media, we have in fact learned to make a silk purse out of a sow&#8217;s ear. Or at least a reasonable approximation of one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rajesh Bhat</title>
		<link>http://tunicca-blog.com/2009/06/24/pre-flight-post-flight-automation/#comment-16</link>
		<dc:creator>Rajesh Bhat</dc:creator>
		<pubDate>Thu, 25 Jun 2009 09:50:41 +0000</pubDate>
		<guid isPermaLink="false">http://tunicca.wordpress.com/?p=348#comment-16</guid>
		<description>Preflight is very important and is one of the best practices to flight check the inputs and outputs of any process. 

The question asked about preflight and post flight is very good. I would rather see it as preflight rather than post flight. One would always call it as post flight as it has been carried after the process, but my opinion to this is Preflight, its always preflight.

Before starting any process, one preflights the job – checks if all the inputs are correct to start the process. He should know the next process where the output generated would serve as an input. On completion of the process, the output is preflighted considering the next process and not the process that one has completed. Hence I would rather call it preflight always rather than post flight. Does this make sense?</description>
		<content:encoded><![CDATA[<p>Preflight is very important and is one of the best practices to flight check the inputs and outputs of any process. </p>
<p>The question asked about preflight and post flight is very good. I would rather see it as preflight rather than post flight. One would always call it as post flight as it has been carried after the process, but my opinion to this is Preflight, its always preflight.</p>
<p>Before starting any process, one preflights the job – checks if all the inputs are correct to start the process. He should know the next process where the output generated would serve as an input. On completion of the process, the output is preflighted considering the next process and not the process that one has completed. Hence I would rather call it preflight always rather than post flight. Does this make sense?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
