<?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: Don&#8217;t Use PICT. Please.</title>
	<atom:link href="http://indesignsecrets.com/dont-use-pict-please.php/feed" rel="self" type="application/rss+xml" />
	<link>http://indesignsecrets.com/dont-use-pict-please.php</link>
	<description>InDesignSecrets Blog and Podcast</description>
	<lastBuildDate>Wed, 23 May 2012 21:37:06 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Yuhong Bao</title>
		<link>http://indesignsecrets.com/dont-use-pict-please.php/comment-page-1#comment-484825</link>
		<dc:creator>Yuhong Bao</dc:creator>
		<pubDate>Thu, 29 Jul 2010 04:12:22 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/?p=2331#comment-484825</guid>
		<description>&quot;According to Adobe’s docs, PICT is still supported. In fact, they even insist that, “The Macintosh PICT (or Picture) format is widely used for Mac OS graphics and page-layout applications, and for transferring files between applications.” Which is a bizarre statement… it is not widely used. And anyone who does “widely use it” should be flogged with a noodle.&quot;
Well, it used to be true, under classic Mac OS and even early Carbon. But while PICTs are not that dangerous IMO, they has been deprecated along with QuickDraw since 10.4. 64-bit apps cannot render PICTs since they have no access to QuickDraw (the few 64-bit APIs that do render PICTs used a 32-bit pictd helper process to do so). If you open one under Preview in Snow Leopard, for example, you will be asked to open the app in 32-bit mode.</description>
		<content:encoded><![CDATA[<p>&#8220;According to Adobe’s docs, PICT is still supported. In fact, they even insist that, “The Macintosh PICT (or Picture) format is widely used for Mac OS graphics and page-layout applications, and for transferring files between applications.” Which is a bizarre statement… it is not widely used. And anyone who does “widely use it” should be flogged with a noodle.&#8221;<br />
Well, it used to be true, under classic Mac OS and even early Carbon. But while PICTs are not that dangerous IMO, they has been deprecated along with QuickDraw since 10.4. 64-bit apps cannot render PICTs since they have no access to QuickDraw (the few 64-bit APIs that do render PICTs used a 32-bit pictd helper process to do so). If you open one under Preview in Snow Leopard, for example, you will be asked to open the app in 32-bit mode.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yuhong Bao</title>
		<link>http://indesignsecrets.com/dont-use-pict-please.php/comment-page-1#comment-484824</link>
		<dc:creator>Yuhong Bao</dc:creator>
		<pubDate>Thu, 29 Jul 2010 04:07:27 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/?p=2331#comment-484824</guid>
		<description>Bob Levine: The reason is that WMF is from 16-bit Windows GDI which did not support these features. Win32 invented EMFs which support all Win32 GDI features. Consider that 16-bit Windows is dead since long ago, EMFs should be used if possible instead of WMFs.</description>
		<content:encoded><![CDATA[<p>Bob Levine: The reason is that WMF is from 16-bit Windows GDI which did not support these features. Win32 invented EMFs which support all Win32 GDI features. Consider that 16-bit Windows is dead since long ago, EMFs should be used if possible instead of WMFs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Bringhurst</title>
		<link>http://indesignsecrets.com/dont-use-pict-please.php/comment-page-1#comment-471438</link>
		<dc:creator>Bob Bringhurst</dc:creator>
		<pubDate>Mon, 22 Dec 2008 18:19:41 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/?p=2331#comment-471438</guid>
		<description>Thanks for the heads up, David. Even though the Help topic warns people not to use PICT files for anything but lo-res printing, we&#039;re still sending a mixed message. I edited the topic to remove all praise of PICT files.</description>
		<content:encoded><![CDATA[<p>Thanks for the heads up, David. Even though the Help topic warns people not to use PICT files for anything but lo-res printing, we&#8217;re still sending a mixed message. I edited the topic to remove all praise of PICT files.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Massey Padgham</title>
		<link>http://indesignsecrets.com/dont-use-pict-please.php/comment-page-1#comment-471423</link>
		<dc:creator>Massey Padgham</dc:creator>
		<pubDate>Sun, 21 Dec 2008 06:38:52 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/?p=2331#comment-471423</guid>
		<description>Many newspapers use PICT for ad placeholders when pages (at least Quark ones) are set up in Layout 8000 (an ad placement/page scheduling program in common use to laydown newspapers). It creates a pict with the name, number etc of the ad. Of course, the real ad comes along later and the Pict was in a print suppressed frame anyway...
But PICT as a production file format. Not.</description>
		<content:encoded><![CDATA[<p>Many newspapers use PICT for ad placeholders when pages (at least Quark ones) are set up in Layout 8000 (an ad placement/page scheduling program in common use to laydown newspapers). It creates a pict with the name, number etc of the ad. Of course, the real ad comes along later and the Pict was in a print suppressed frame anyway&#8230;<br />
But PICT as a production file format. Not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joecab</title>
		<link>http://indesignsecrets.com/dont-use-pict-please.php/comment-page-1#comment-471419</link>
		<dc:creator>joecab</dc:creator>
		<pubDate>Sat, 20 Dec 2008 23:41:19 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/?p=2331#comment-471419</guid>
		<description>&gt; Then get with the times man!

I know, I know *groan*

I always resave JPEG files as TIFF. Why? I&#039;m paranoid, and I don&#039;t want to risk someone else working on those JPEGs without realizing that they may not be working with it at maximum quality. Better to just take that x factor out entirely.</description>
		<content:encoded><![CDATA[<p>&gt; Then get with the times man!</p>
<p>I know, I know *groan*</p>
<p>I always resave JPEG files as TIFF. Why? I&#8217;m paranoid, and I don&#8217;t want to risk someone else working on those JPEGs without realizing that they may not be working with it at maximum quality. Better to just take that x factor out entirely.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Levine</title>
		<link>http://indesignsecrets.com/dont-use-pict-please.php/comment-page-1#comment-471384</link>
		<dc:creator>Bob Levine</dc:creator>
		<pubDate>Fri, 19 Dec 2008 18:20:08 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/?p=2331#comment-471384</guid>
		<description>I have a client...a very large international company with many subsidiaries that uses an automated system to insert the proper logos into Word and Powerpoint.

In order to work properly they can&#039;t be scaled...CorelDRAW to the rescue!</description>
		<content:encoded><![CDATA[<p>I have a client&#8230;a very large international company with many subsidiaries that uses an automated system to insert the proper logos into Word and Powerpoint.</p>
<p>In order to work properly they can&#8217;t be scaled&#8230;CorelDRAW to the rescue!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eugene</title>
		<link>http://indesignsecrets.com/dont-use-pict-please.php/comment-page-1#comment-471379</link>
		<dc:creator>Eugene</dc:creator>
		<pubDate>Fri, 19 Dec 2008 16:02:20 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/?p=2331#comment-471379</guid>
		<description>Hey Bob, that&#039;s why when I make an file for MS office in Illustrator I make it roughly 2 or 3 times larger than it would be needed. 

When it&#039;s brought into MS office it needs to be scaled down to the right size. It&#039;s very rare that anyone using MS Office would print or display their slideshows in anything larger than A4. So making the image A3 or A2 size in Illustrator then exporting to WMF definitely accounts for that.

And when have you met anyone that uses non-pro apps who are fussy how they&#039;re print stuff prints anyway? (insert wink smiley)</description>
		<content:encoded><![CDATA[<p>Hey Bob, that&#8217;s why when I make an file for MS office in Illustrator I make it roughly 2 or 3 times larger than it would be needed. </p>
<p>When it&#8217;s brought into MS office it needs to be scaled down to the right size. It&#8217;s very rare that anyone using MS Office would print or display their slideshows in anything larger than A4. So making the image A3 or A2 size in Illustrator then exporting to WMF definitely accounts for that.</p>
<p>And when have you met anyone that uses non-pro apps who are fussy how they&#8217;re print stuff prints anyway? (insert wink smiley)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Levine</title>
		<link>http://indesignsecrets.com/dont-use-pict-please.php/comment-page-1#comment-471377</link>
		<dc:creator>Bob Levine</dc:creator>
		<pubDate>Fri, 19 Dec 2008 15:50:30 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/?p=2331#comment-471377</guid>
		<description>Re: WMFs

They&#039;re horrible format for high end use with no support that I know of for bezier curves or CMYK. This means that when you convert a file to WMF all curves are converted to small line segments and CMYK colors are converted to RGB.

When you scale those files up the lack of bezier support becomes very apparent. FWIW, I find Illustrator&#039;s capability to save as WMF insufficient even for Office apps leaving curves looking very jagged.

When I need a WMF I use CorelDRAW which does a much better job.</description>
		<content:encoded><![CDATA[<p>Re: WMFs</p>
<p>They&#8217;re horrible format for high end use with no support that I know of for bezier curves or CMYK. This means that when you convert a file to WMF all curves are converted to small line segments and CMYK colors are converted to RGB.</p>
<p>When you scale those files up the lack of bezier support becomes very apparent. FWIW, I find Illustrator&#8217;s capability to save as WMF insufficient even for Office apps leaving curves looking very jagged.</p>
<p>When I need a WMF I use CorelDRAW which does a much better job.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eugene</title>
		<link>http://indesignsecrets.com/dont-use-pict-please.php/comment-page-1#comment-471375</link>
		<dc:creator>Eugene</dc:creator>
		<pubDate>Fri, 19 Dec 2008 15:06:57 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/?p=2331#comment-471375</guid>
		<description>SVG is currently a web type of image. I wouldn&#039;t risk using it in a printing workflow. It&#039;s bascially a vgml (vector graphic markup language) and I think it&#039;s done with xml. Because of this it can contain scripting and animations and things like that. As far as I know it&#039;s fine to save these as PDF as the pdf coding preserves all the vectors. As well as being a web graphic it would probably all RGB, so I&#039;m not sure how that translates into CMYK? But as it&#039;s xml it could contain weird things and require extra proofing, like scripts and animations etc. There is a SVG print format being worked on at the moment by W3C with Adobe and Corel and a few others but I&#039;m not sure how far along that is?

I&#039;m a little sketchy on the details, I&#039;ll admit. But I think it&#039;s best to save it as a PDF to avoid unforeseen headaches.</description>
		<content:encoded><![CDATA[<p>SVG is currently a web type of image. I wouldn&#8217;t risk using it in a printing workflow. It&#8217;s bascially a vgml (vector graphic markup language) and I think it&#8217;s done with xml. Because of this it can contain scripting and animations and things like that. As far as I know it&#8217;s fine to save these as PDF as the pdf coding preserves all the vectors. As well as being a web graphic it would probably all RGB, so I&#8217;m not sure how that translates into CMYK? But as it&#8217;s xml it could contain weird things and require extra proofing, like scripts and animations etc. There is a SVG print format being worked on at the moment by W3C with Adobe and Corel and a few others but I&#8217;m not sure how far along that is?</p>
<p>I&#8217;m a little sketchy on the details, I&#8217;ll admit. But I think it&#8217;s best to save it as a PDF to avoid unforeseen headaches.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kim  Bach</title>
		<link>http://indesignsecrets.com/dont-use-pict-please.php/comment-page-1#comment-471374</link>
		<dc:creator>Kim  Bach</dc:creator>
		<pubDate>Fri, 19 Dec 2008 14:52:46 +0000</pubDate>
		<guid isPermaLink="false">http://indesignsecrets.com/?p=2331#comment-471374</guid>
		<description>What about using open formats like SVG?</description>
		<content:encoded><![CDATA[<p>What about using open formats like SVG?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (enhanced) (user agent is rejected)
Database Caching using disk

Served from: indesignsecrets.com @ 2012-05-23 22:35:22 -->
