<?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: Do you use PICT?</title>
	<atom:link href="http://blogs.adobe.com/jnack/2009/04/do_you_use_pict.html/feed" rel="self" type="application/rss+xml" />
	<link>http://blogs.adobe.com/jnack/2009/04/do_you_use_pict.html</link>
	<description></description>
	<lastBuildDate>Thu, 20 Jun 2013 01:19:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: victoria</title>
		<link>http://blogs.adobe.com/jnack/2009/04/do_you_use_pict.html#comment-34551</link>
		<dc:creator>victoria</dc:creator>
		<pubDate>Wed, 27 Apr 2011 21:00:44 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2009/04/do-you-use-pict.html#comment-34551</guid>
		<description><![CDATA[I use PICT FILES for a lot of my Graphic as an overlay, because they are not as big as a PSD so less space and work fast in my programs to zoom adjust photos.  Can you please tell me an alternate way to get this IF PICT FILES are no longer available.]]></description>
		<content:encoded><![CDATA[<p>I use PICT FILES for a lot of my Graphic as an overlay, because they are not as big as a PSD so less space and work fast in my programs to zoom adjust photos.  Can you please tell me an alternate way to get this IF PICT FILES are no longer available.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Gurney</title>
		<link>http://blogs.adobe.com/jnack/2009/04/do_you_use_pict.html#comment-20668</link>
		<dc:creator>Ben Gurney</dc:creator>
		<pubDate>Thu, 08 Jul 2010 20:10:32 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2009/04/do-you-use-pict.html#comment-20668</guid>
		<description><![CDATA[I use pict files all the time. I know it&#039;s an old format but it works great in After Effects, Flash, Premiere, and Final Cut Pro. I always know it&#039;s going to be RGB, and the file sizes are small. I am disappointed that it was removed, but I guess I need to change.]]></description>
		<content:encoded><![CDATA[<p>I use pict files all the time. I know it&#8217;s an old format but it works great in After Effects, Flash, Premiere, and Final Cut Pro. I always know it&#8217;s going to be RGB, and the file sizes are small. I am disappointed that it was removed, but I guess I need to change.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Destination Wedding Photography</title>
		<link>http://blogs.adobe.com/jnack/2009/04/do_you_use_pict.html#comment-11909</link>
		<dc:creator>Destination Wedding Photography</dc:creator>
		<pubDate>Tue, 08 Dec 2009 23:36:21 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2009/04/do-you-use-pict.html#comment-11909</guid>
		<description><![CDATA[Fort Myers, Wedding and Photography offers a good mixture of direction and photography tips for beginners, and handy hints for the more experienced.
]]></description>
		<content:encoded><![CDATA[<p>Fort Myers, Wedding and Photography offers a good mixture of direction and photography tips for beginners, and handy hints for the more experienced.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: barnaby hall</title>
		<link>http://blogs.adobe.com/jnack/2009/04/do_you_use_pict.html#comment-11908</link>
		<dc:creator>barnaby hall</dc:creator>
		<pubDate>Thu, 05 Nov 2009 08:58:20 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2009/04/do-you-use-pict.html#comment-11908</guid>
		<description><![CDATA[This discussion is WAY above my tiny head. My principal concern, as a photographer who has used Photoshop quite successfully -in a primitive  analogue kind of a way for some time- is how to avoid the horrendous frustration of compatibility and unexpected change. Recently my trusty PowerBook G4 &quot;broke&quot; and was diagnosed with lower RAM slot failure (apparently a known issue that is currently being thrashed out by infuriated Apple clients and Apple).
I was advised to get important files out fast and buy a new laptop. Reluctantly I did this. I was assured that migration of all my previous software etc would be seamless, painless and that I would be delighted  with the end result. It would be as if nothing ever happened. Hmm.
The result of this, so far, is that I am unable to use my Epson printer and photoshop CS (the first one) is not functioning at all well. I´m sure it will be resolved eventually however I am angry to find that until then my expensive new MacBook pro with Snow Leopard is only good for internet and I´m forced to use my lame old G4 to print or work in Photoshop. I have nothing against progress and change at all. BUT I don´t think one should &quot;forced &quot; into it just when one has finally found a comfortable  and efficient style of working.
I realize this has nothing to do with this discussion thread but I ´m venting wherever I can. Forgive me.
]]></description>
		<content:encoded><![CDATA[<p>This discussion is WAY above my tiny head. My principal concern, as a photographer who has used Photoshop quite successfully -in a primitive  analogue kind of a way for some time- is how to avoid the horrendous frustration of compatibility and unexpected change. Recently my trusty PowerBook G4 &#8220;broke&#8221; and was diagnosed with lower RAM slot failure (apparently a known issue that is currently being thrashed out by infuriated Apple clients and Apple).<br />
I was advised to get important files out fast and buy a new laptop. Reluctantly I did this. I was assured that migration of all my previous software etc would be seamless, painless and that I would be delighted  with the end result. It would be as if nothing ever happened. Hmm.<br />
The result of this, so far, is that I am unable to use my Epson printer and photoshop CS (the first one) is not functioning at all well. I´m sure it will be resolved eventually however I am angry to find that until then my expensive new MacBook pro with Snow Leopard is only good for internet and I´m forced to use my lame old G4 to print or work in Photoshop. I have nothing against progress and change at all. BUT I don´t think one should &#8220;forced &#8221; into it just when one has finally found a comfortable  and efficient style of working.<br />
I realize this has nothing to do with this discussion thread but I ´m venting wherever I can. Forgive me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chad</title>
		<link>http://blogs.adobe.com/jnack/2009/04/do_you_use_pict.html#comment-11907</link>
		<dc:creator>Chad</dc:creator>
		<pubDate>Thu, 07 May 2009 19:56:14 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2009/04/do-you-use-pict.html#comment-11907</guid>
		<description><![CDATA[Hmm...I think I used the PICT format 20 years ago on a Mac Classic.
Even if it wasn&#039;t that long ago, it seems like it.  No worries here, most of the graphics I work with are for the web or Mac applications.
]]></description>
		<content:encoded><![CDATA[<p>Hmm&#8230;I think I used the PICT format 20 years ago on a Mac Classic.<br />
Even if it wasn&#8217;t that long ago, it seems like it.  No worries here, most of the graphics I work with are for the web or Mac applications.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geoff</title>
		<link>http://blogs.adobe.com/jnack/2009/04/do_you_use_pict.html#comment-11906</link>
		<dc:creator>Geoff</dc:creator>
		<pubDate>Tue, 05 May 2009 21:47:52 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2009/04/do-you-use-pict.html#comment-11906</guid>
		<description><![CDATA[I have a lot of content in pict files backed up on CDs that I hope to someday compile into a texture and stock photo library. Please don&#039;t make me have to buy DeBabelizer or some other obscure graphics converter tool in order to use old file formats. What&#039;s the harm in leaving in old formats? It&#039;s not like HD space or RAM is getting more expensive.
]]></description>
		<content:encoded><![CDATA[<p>I have a lot of content in pict files backed up on CDs that I hope to someday compile into a texture and stock photo library. Please don&#8217;t make me have to buy DeBabelizer or some other obscure graphics converter tool in order to use old file formats. What&#8217;s the harm in leaving in old formats? It&#8217;s not like HD space or RAM is getting more expensive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aaron breckenridge</title>
		<link>http://blogs.adobe.com/jnack/2009/04/do_you_use_pict.html#comment-11905</link>
		<dc:creator>aaron breckenridge</dc:creator>
		<pubDate>Tue, 05 May 2009 10:42:59 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2009/04/do-you-use-pict.html#comment-11905</guid>
		<description><![CDATA[Ryan,
Wow, thanks for the tip about MS Office. Word opens these just fine, even when Apple has left the format in the dust.
]]></description>
		<content:encoded><![CDATA[<p>Ryan,<br />
Wow, thanks for the tip about MS Office. Word opens these just fine, even when Apple has left the format in the dust.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://blogs.adobe.com/jnack/2009/04/do_you_use_pict.html#comment-11904</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Mon, 04 May 2009 20:44:32 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2009/04/do-you-use-pict.html#comment-11904</guid>
		<description><![CDATA[As much as I hate to admit it, a quick search with Spotlight revealed that I used PICT in a project as recently as 2003 (just before moving from OS 9 to OS X actually). Have avoided them since OS X in favour of newer, better supported formats.
However, there are some very new PICT images on my computer — in the form of about a hundred PICT &lt;b&gt;Clipart images&lt;/b&gt; installed with Microsoft Office 2008! Unbelievable!
]]></description>
		<content:encoded><![CDATA[<p>As much as I hate to admit it, a quick search with Spotlight revealed that I used PICT in a project as recently as 2003 (just before moving from OS 9 to OS X actually). Have avoided them since OS X in favour of newer, better supported formats.<br />
However, there are some very new PICT images on my computer — in the form of about a hundred PICT <b>Clipart images</b> installed with Microsoft Office 2008! Unbelievable!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamie Reid</title>
		<link>http://blogs.adobe.com/jnack/2009/04/do_you_use_pict.html#comment-11903</link>
		<dc:creator>Jamie Reid</dc:creator>
		<pubDate>Mon, 04 May 2009 20:08:18 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2009/04/do-you-use-pict.html#comment-11903</guid>
		<description><![CDATA[A number of indie/shareware games on the Mac use PICT for textures. Some of them support any Quicktime-supported format, but some don&#039;t.
All my intermediate work is stored as .PSDs, though, so I don&#039;t care that much if it&#039;s deprecated. Would be nice if there was at least a read-only PICT option.
]]></description>
		<content:encoded><![CDATA[<p>A number of indie/shareware games on the Mac use PICT for textures. Some of them support any Quicktime-supported format, but some don&#8217;t.<br />
All my intermediate work is stored as .PSDs, though, so I don&#8217;t care that much if it&#8217;s deprecated. Would be nice if there was at least a read-only PICT option.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Buchheim</title>
		<link>http://blogs.adobe.com/jnack/2009/04/do_you_use_pict.html#comment-11902</link>
		<dc:creator>Tim Buchheim</dc:creator>
		<pubDate>Mon, 04 May 2009 15:48:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2009/04/do-you-use-pict.html#comment-11902</guid>
		<description><![CDATA[I love the idea of a Colbert-style &quot;on notice&quot; board. :-)
Apple put PICT &quot;on notice&quot; years ago, when it deprecated QuickDraw.  For those that don&#039;t know, PICT is very closely tied to QuickDraw.  A PICT file is essentially a list of stored QuickDraw drawing commands.  Currently it&#039;s easy for Photoshop or any other program to use PICT.. you just ask QuickDraw to replay the list of drawing commands.  Creating a PICT is as simple as saying &quot;hey QuickDraw, I&#039;m starting a PICT&quot;, then issuing normal QuickDraw drawing commands (eg. &quot;draw a rectangle here&quot;, &quot;draw a line there&quot;) and then letting QuickDraw know when you&#039;re done.  It spits out a PICT, ready for saving to disk.
But when QuickDraw goes away (as it has in the 64-bit runtime) then that easy way of supporting PICT goes away too.  The easiest way to deal with it is to have a separate (32-bit) process do these steps, but that gets messy.  And doesn&#039;t get around the fact that Apple has been pushing developers for years and years now to stop using QuickDraw.
re Carbon/Cocoa:  Cocoa and Carbon exist side-by-side.  Neither is built &quot;on top of&quot; the other.  They&#039;re both built on top of some shared frameworks, such as Core Foundation, Core Graphics (aka Quartz), Core Audio, and so on.  Current versions of Cocoa make use of a few Carbon functions (most notably for drawing menus) but that&#039;s going away.   And even the parts of Carbon used by the current version of Cocoa don&#039;t use QuickDraw anymore.  QuickDraw has been dead for years, with only its rotting corpse hanging around to keep ancient applications like Photoshop  and Office running.  And Apple&#039;s recent actions (such as leaving it out of their 64-bit libraries) have finally killed it for good.  (And it&#039;s about time.  While QuickDraw was wonderful back in the 80s, it just hasn&#039;t kept up with modern demands.)
I&#039;d go with a separate &quot;Convert PICT to PDF&quot; utility if people really insist on PDF support. (Or just tell people to use Preview.)
]]></description>
		<content:encoded><![CDATA[<p>I love the idea of a Colbert-style &#8220;on notice&#8221; board. :-)<br />
Apple put PICT &#8220;on notice&#8221; years ago, when it deprecated QuickDraw.  For those that don&#8217;t know, PICT is very closely tied to QuickDraw.  A PICT file is essentially a list of stored QuickDraw drawing commands.  Currently it&#8217;s easy for Photoshop or any other program to use PICT.. you just ask QuickDraw to replay the list of drawing commands.  Creating a PICT is as simple as saying &#8220;hey QuickDraw, I&#8217;m starting a PICT&#8221;, then issuing normal QuickDraw drawing commands (eg. &#8220;draw a rectangle here&#8221;, &#8220;draw a line there&#8221;) and then letting QuickDraw know when you&#8217;re done.  It spits out a PICT, ready for saving to disk.<br />
But when QuickDraw goes away (as it has in the 64-bit runtime) then that easy way of supporting PICT goes away too.  The easiest way to deal with it is to have a separate (32-bit) process do these steps, but that gets messy.  And doesn&#8217;t get around the fact that Apple has been pushing developers for years and years now to stop using QuickDraw.<br />
re Carbon/Cocoa:  Cocoa and Carbon exist side-by-side.  Neither is built &#8220;on top of&#8221; the other.  They&#8217;re both built on top of some shared frameworks, such as Core Foundation, Core Graphics (aka Quartz), Core Audio, and so on.  Current versions of Cocoa make use of a few Carbon functions (most notably for drawing menus) but that&#8217;s going away.   And even the parts of Carbon used by the current version of Cocoa don&#8217;t use QuickDraw anymore.  QuickDraw has been dead for years, with only its rotting corpse hanging around to keep ancient applications like Photoshop  and Office running.  And Apple&#8217;s recent actions (such as leaving it out of their 64-bit libraries) have finally killed it for good.  (And it&#8217;s about time.  While QuickDraw was wonderful back in the 80s, it just hasn&#8217;t kept up with modern demands.)<br />
I&#8217;d go with a separate &#8220;Convert PICT to PDF&#8221; utility if people really insist on PDF support. (Or just tell people to use Preview.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Colin Holgate</title>
		<link>http://blogs.adobe.com/jnack/2009/04/do_you_use_pict.html#comment-11901</link>
		<dc:creator>Colin Holgate</dc:creator>
		<pubDate>Mon, 04 May 2009 06:54:38 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2009/04/do-you-use-pict.html#comment-11901</guid>
		<description><![CDATA[There are two type of PICT, the one that was a container for lots of vector graphics, and the one that is usually a RLE compressed bitmap. Dropping the vector graphics one would be ok, but If you drop PICT, you should also drop support for BMP.
As for use of PICT in workflow, we&#039;ve used it a lot as a way to show a flat image of a design, that is still possible to pick colors from. Using JPEG won&#039;t do, the colors are all changed. Using PNG would often lead to unintended premultiplied colors being present. It was possible to explain carefully how to do a Save For Web to avoid the PNG issue, but it was much easier just to say to save a flat PICT.
Now, arguably anyone with PS CS5 will have the improved PNG saving, so as long as you don&#039;t rip out PICT support from CS4, we&#039;ll all survive! Hopefully someone with Director 12 and PS CS5 will still be able to edit bitmap cast members without PS complaining about it being too much like a PICT.
]]></description>
		<content:encoded><![CDATA[<p>There are two type of PICT, the one that was a container for lots of vector graphics, and the one that is usually a RLE compressed bitmap. Dropping the vector graphics one would be ok, but If you drop PICT, you should also drop support for BMP.<br />
As for use of PICT in workflow, we&#8217;ve used it a lot as a way to show a flat image of a design, that is still possible to pick colors from. Using JPEG won&#8217;t do, the colors are all changed. Using PNG would often lead to unintended premultiplied colors being present. It was possible to explain carefully how to do a Save For Web to avoid the PNG issue, but it was much easier just to say to save a flat PICT.<br />
Now, arguably anyone with PS CS5 will have the improved PNG saving, so as long as you don&#8217;t rip out PICT support from CS4, we&#8217;ll all survive! Hopefully someone with Director 12 and PS CS5 will still be able to edit bitmap cast members without PS complaining about it being too much like a PICT.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bobby</title>
		<link>http://blogs.adobe.com/jnack/2009/04/do_you_use_pict.html#comment-11900</link>
		<dc:creator>Bobby</dc:creator>
		<pubDate>Tue, 21 Apr 2009 05:24:19 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2009/04/do-you-use-pict.html#comment-11900</guid>
		<description><![CDATA[We use pict files on a regular basis. If you were to eliminate the feature, we would be unable to deliver project needs to our vendors. We do lots of video, and it&#039;s my job to deliver the graphics files in required formats.  Please don&#039;t do away with picts!
]]></description>
		<content:encoded><![CDATA[<p>We use pict files on a regular basis. If you were to eliminate the feature, we would be unable to deliver project needs to our vendors. We do lots of video, and it&#8217;s my job to deliver the graphics files in required formats.  Please don&#8217;t do away with picts!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Chandler</title>
		<link>http://blogs.adobe.com/jnack/2009/04/do_you_use_pict.html#comment-11899</link>
		<dc:creator>Scott Chandler</dc:creator>
		<pubDate>Sat, 18 Apr 2009 15:51:30 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2009/04/do-you-use-pict.html#comment-11899</guid>
		<description><![CDATA[I have a number of workflows that still use PICT. Even if that were to change today, I would still have hundred of PICTs (many of them long since archived but still referenced once in a while) that would be essentially unreadable since Preview no longer opens them.
]]></description>
		<content:encoded><![CDATA[<p>I have a number of workflows that still use PICT. Even if that were to change today, I would still have hundred of PICTs (many of them long since archived but still referenced once in a while) that would be essentially unreadable since Preview no longer opens them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Twardoch</title>
		<link>http://blogs.adobe.com/jnack/2009/04/do_you_use_pict.html#comment-11898</link>
		<dc:creator>Adam Twardoch</dc:creator>
		<pubDate>Fri, 17 Apr 2009 19:07:45 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2009/04/do-you-use-pict.html#comment-11898</guid>
		<description><![CDATA[John,
I use CS4 apps to do a lot of low-level office document engineering.
PICT just like WMF or EMF are essential formats in the office world. Microsoft Office natively uses WMF and EMF while iWork uses PICT. The newest office file formats (iWork and Office 2007/2008) are ZIP archives containing XML files along with graphical resources.
In case of iWork files (such as those created in Pages), the images are often saved in PICT format. For example, if I install MathType 6 for Mac and insert a MathType equation into Pages, and then save the document as a .pages file, after unzipping the .pages file, inside the folder I will have a vector-based PICT file containing the rendering of the equation. There are situations when I would like to open that PICT file, examine it, edit it, perhaps convert it to PDF etc.
So, PICT just like EMF and WMF are essential.
Regards,
Adam Twardoch
]]></description>
		<content:encoded><![CDATA[<p>John,<br />
I use CS4 apps to do a lot of low-level office document engineering.<br />
PICT just like WMF or EMF are essential formats in the office world. Microsoft Office natively uses WMF and EMF while iWork uses PICT. The newest office file formats (iWork and Office 2007/2008) are ZIP archives containing XML files along with graphical resources.<br />
In case of iWork files (such as those created in Pages), the images are often saved in PICT format. For example, if I install MathType 6 for Mac and insert a MathType equation into Pages, and then save the document as a .pages file, after unzipping the .pages file, inside the folder I will have a vector-based PICT file containing the rendering of the equation. There are situations when I would like to open that PICT file, examine it, edit it, perhaps convert it to PDF etc.<br />
So, PICT just like EMF and WMF are essential.<br />
Regards,<br />
Adam Twardoch</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith Humm</title>
		<link>http://blogs.adobe.com/jnack/2009/04/do_you_use_pict.html#comment-11897</link>
		<dc:creator>Keith Humm</dc:creator>
		<pubDate>Thu, 16 Apr 2009 17:12:40 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2009/04/do-you-use-pict.html#comment-11897</guid>
		<description><![CDATA[We use PICTs here maybe once a month? Never write them, but reading old files is extremely handy.
It&#039;s not a huge deal for us to run a converter, but that converter really should come with Photoshop - either as a separate utility or as part of the app.
]]></description>
		<content:encoded><![CDATA[<p>We use PICTs here maybe once a month? Never write them, but reading old files is extremely handy.<br />
It&#8217;s not a huge deal for us to run a converter, but that converter really should come with Photoshop &#8211; either as a separate utility or as part of the app.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
