<br />
<b>Warning</b>:  include() [<a href='function.include'>function.include</a>]: Unable to access /var/www/html/rogue-development/blog2/wp-content/advanced-cache.php in <b>/var/www/html/rogue-development/blog2/wp-settings.php</b> on line <b>62</b><br />
<br />
<b>Warning</b>:  include(/var/www/html/rogue-development/blog2/wp-content/advanced-cache.php) [<a href='function.include'>function.include</a>]: failed to open stream: No such file or directory in <b>/var/www/html/rogue-development/blog2/wp-settings.php</b> on line <b>62</b><br />
<br />
<b>Warning</b>:  include() [<a href='function.include'>function.include</a>]: Failed opening '/var/www/html/rogue-development/blog2/wp-content/advanced-cache.php' for inclusion (include_path='.:/usr/share/pear:/usr/share/php') in <b>/var/www/html/rogue-development/blog2/wp-settings.php</b> on line <b>62</b><br />
<br />
<b>Notice</b>:  add_option was called with an argument that is <strong>deprecated</strong> since version 2.3 with no alternative available. in <b>/var/www/html/rogue-development/blog2/wp-includes/functions.php</b> on line <b>3468</b><br />
<br />
<b>Notice</b>:  register_sidebar_widget is <strong>deprecated</strong> since version 2.8! Use wp_register_sidebar_widget() instead. in <b>/var/www/html/rogue-development/blog2/wp-includes/functions.php</b> on line <b>3382</b><br />
<br />
<b>Notice</b>:  register_widget_control is <strong>deprecated</strong> since version 2.8! Use wp_register_widget_control() instead. in <b>/var/www/html/rogue-development/blog2/wp-includes/functions.php</b> on line <b>3382</b><br />
<?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 on: Printing horrors</title>
	<atom:link href="http://www.rogue-development.com/blog2/2008/06/printing-horrors/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rogue-development.com/blog2/2008/06/printing-horrors/</link>
	<description>Comments and thoughts on technology from Marc Hughes</description>
	<lastBuildDate>Sun, 30 Jan 2011 18:36:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Will</title>
		<link>http://www.rogue-development.com/blog2/2008/06/printing-horrors/comment-page-1/#comment-389</link>
		<dc:creator>Will</dc:creator>
		<pubDate>Sat, 26 Jul 2008 01:35:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.rogue-development.com/blog2/?p=219#comment-389</guid>
		<description>Developing for AIR on Mac OS X.  The FlexPrintJob.printAsBitmap = false does not seem to do anything for me.  Printed text is fuzzy.</description>
		<content:encoded><![CDATA[<p>Developing for AIR on Mac OS X.  The FlexPrintJob.printAsBitmap = false does not seem to do anything for me.  Printed text is fuzzy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc</title>
		<link>http://www.rogue-development.com/blog2/2008/06/printing-horrors/comment-page-1/#comment-350</link>
		<dc:creator>Marc</dc:creator>
		<pubDate>Fri, 20 Jun 2008 11:42:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.rogue-development.com/blog2/?p=219#comment-350</guid>
		<description>Theo, like I mentioned the OSX printouts were a bit blurrier than windows.  But we&#039;re making multi-page timelines that get printed out and hanged on a wall.  So the intended target audience is standing back a few feet.  Maybe our requirements are just a bit less stringent than yours.

Das,
printAsBitmap true/false doesn&#039;t seem to do a lot for us.</description>
		<content:encoded><![CDATA[<p>Theo, like I mentioned the OSX printouts were a bit blurrier than windows.  But we&#8217;re making multi-page timelines that get printed out and hanged on a wall.  So the intended target audience is standing back a few feet.  Maybe our requirements are just a bit less stringent than yours.</p>
<p>Das,<br />
printAsBitmap true/false doesn&#8217;t seem to do a lot for us.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DasFX</title>
		<link>http://www.rogue-development.com/blog2/2008/06/printing-horrors/comment-page-1/#comment-349</link>
		<dc:creator>DasFX</dc:creator>
		<pubDate>Thu, 19 Jun 2008 21:37:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.rogue-development.com/blog2/?p=219#comment-349</guid>
		<description>Anyone notice any difference when setting FlexPrintJob.printAsBitmap to false?</description>
		<content:encoded><![CDATA[<p>Anyone notice any difference when setting FlexPrintJob.printAsBitmap to false?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Theo</title>
		<link>http://www.rogue-development.com/blog2/2008/06/printing-horrors/comment-page-1/#comment-348</link>
		<dc:creator>Theo</dc:creator>
		<pubDate>Thu, 19 Jun 2008 17:03:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.rogue-development.com/blog2/?p=219#comment-348</guid>
		<description>I&#039;ve tried printing components containing text rendered with both device fonts (the default, Verdana) and embedded fonts on OS X the printed text is really, really blurry. Printing a 72 dpi bitmap with text doesn&#039;t look as blurry as this does, it must be something wrong with the way Flash/Flex prepares the print job, at least on the Mac. You would expect something that&#039;s basically vectors all the way to do crisp printing, instead it looks like a bitmap rendering at 50 dpi blown up to 300.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve tried printing components containing text rendered with both device fonts (the default, Verdana) and embedded fonts on OS X the printed text is really, really blurry. Printing a 72 dpi bitmap with text doesn&#8217;t look as blurry as this does, it must be something wrong with the way Flash/Flex prepares the print job, at least on the Mac. You would expect something that&#8217;s basically vectors all the way to do crisp printing, instead it looks like a bitmap rendering at 50 dpi blown up to 300.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Throop</title>
		<link>http://www.rogue-development.com/blog2/2008/06/printing-horrors/comment-page-1/#comment-347</link>
		<dc:creator>Ben Throop</dc:creator>
		<pubDate>Tue, 17 Jun 2008 21:33:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.rogue-development.com/blog2/?p=219#comment-347</guid>
		<description>I print directly from the Display List too and it does keep things as vector. In fact, the Canvas I&#039;m printing from is only around 425 x 550 (Half of 8.5 x 11 times 100px), and it&#039;s not blurry at all. The only error I&#039;m seeing is that I get an extremely thin blue line on the left and bottom of the image in the print. Strangely, it only happens when I do a physical print - when I print to PDF it doesn&#039;t show up. Anyone ever see that?</description>
		<content:encoded><![CDATA[<p>I print directly from the Display List too and it does keep things as vector. In fact, the Canvas I&#8217;m printing from is only around 425 x 550 (Half of 8.5 x 11 times 100px), and it&#8217;s not blurry at all. The only error I&#8217;m seeing is that I get an extremely thin blue line on the left and bottom of the image in the print. Strangely, it only happens when I do a physical print &#8211; when I print to PDF it doesn&#8217;t show up. Anyone ever see that?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc</title>
		<link>http://www.rogue-development.com/blog2/2008/06/printing-horrors/comment-page-1/#comment-346</link>
		<dc:creator>Marc</dc:creator>
		<pubDate>Tue, 17 Jun 2008 17:38:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.rogue-development.com/blog2/?p=219#comment-346</guid>
		<description>We had some problems when capturing a bitmap and then printing that with bluriness.  The problem is the printer has a much higher DPI than the screen so the anti-aliasing is all wrong and gives a blurry look.

But we moved to a scheme where we print directly from a display object to the PrintJob and it&#039;s working pretty well.  I assume it&#039;s keeping the vector graphics until a later stage in the process.  On OSX it&#039;s slightly blurry and on Windows it&#039;s perfect.

We are using system rendered and not embedded fonts.</description>
		<content:encoded><![CDATA[<p>We had some problems when capturing a bitmap and then printing that with bluriness.  The problem is the printer has a much higher DPI than the screen so the anti-aliasing is all wrong and gives a blurry look.</p>
<p>But we moved to a scheme where we print directly from a display object to the PrintJob and it&#8217;s working pretty well.  I assume it&#8217;s keeping the vector graphics until a later stage in the process.  On OSX it&#8217;s slightly blurry and on Windows it&#8217;s perfect.</p>
<p>We are using system rendered and not embedded fonts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Theo</title>
		<link>http://www.rogue-development.com/blog2/2008/06/printing-horrors/comment-page-1/#comment-345</link>
		<dc:creator>Theo</dc:creator>
		<pubDate>Tue, 17 Jun 2008 17:26:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.rogue-development.com/blog2/?p=219#comment-345</guid>
		<description>Do you have any tips on making the quality acceptable? I&#039;ve tried printing directly from Flex with PrintJob but the quality is awful, it&#039;s all blurry. Have I missed something?</description>
		<content:encoded><![CDATA[<p>Do you have any tips on making the quality acceptable? I&#8217;ve tried printing directly from Flex with PrintJob but the quality is awful, it&#8217;s all blurry. Have I missed something?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

