<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Gabriel de Kadt &#187; transparency</title>
	<atom:link href="http://www.lazydada.com/tag/transparency/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lazydada.com</link>
	<description>Personal notes on Mac based web development and design.</description>
	<lastBuildDate>Tue, 03 Aug 2010 18:01:24 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Illustrator PDF reply on Adobe forums</title>
		<link>http://www.lazydada.com/2007-11-10/illustrator-pdf-reply-on-adobe-forums/</link>
		<comments>http://www.lazydada.com/2007-11-10/illustrator-pdf-reply-on-adobe-forums/#comments</comments>
		<pubDate>Sat, 10 Nov 2007 17:09:31 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Graphic arts]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[Adobe Illustrator]]></category>
		<category><![CDATA[PDF]]></category>
		<category><![CDATA[transparency]]></category>

		<guid isPermaLink="false">http://www.lazydada.com/2007-11-10/illustrator-pdf-reply-on-adobe-forums/</guid>
		<description><![CDATA[What I said was… There are many pitfalls to be avoided when working in Illustrator. Beyond it being buggy and a hog I find it&#8217;s not a great tool for working on any press-ready artwork. [Disclosure: InDesign fanboy here]. Firstly, as Aandi notes, avoid flattening artwork (ie printing to PostScript or saving as PDF 1.3 [...]]]></description>
			<content:encoded><![CDATA[<p>What I said was…</p>
<blockquote><p>There are many pitfalls to be avoided when working in Illustrator. Beyond it being buggy and a hog I find it&#8217;s not a great tool for working on any press-ready artwork. [Disclosure: InDesign fanboy here]. </p>
<p>Firstly, as Aandi notes, avoid flattening artwork (ie printing to PostScript or saving as PDF 1.3 or under) &#8211; as that causes many transparency effects, including drop-shadows, to be converted into raster art. </p>
<p>If you must export flattened artwork don&#8217;t forget to set the &#8220;Document Raster Effects Settings&#8221; (under Effect on the menu bar) to a suitable level. Unfortunately the default is 72dpi. </p>
<p>Also ensure that any important type or vector information is kept in a separate layer above &#8220;background&#8221; objects. The idea is to add a virtual layer of separation between type and effects. &#8220;In Front&#8221; and &#8220;Behind&#8221; is not enough &#8211; use layers. [The same applies for InDesign.] </p>
<p>Again Aandi is spot on: the &#8220;Save PDF with editing capability&#8221; feature can cause massive file sizes; the difference with the PDF of the cover of the magazine I work on: a few hundred MB or just a few MB! </p>
<p>Another thing try to remember to use &#8220;Save a Copy&#8221; or to otherwise be careful not to get your final delivery artwork confused with the working file. Its&#8217;s an inherent confusion in Illustrator: PDFs should really only be used as final artwork &#8211; not as a working file. I don&#8217;t like that at all. Particularly as I have to deal with these ambiguous duplicate files at work. Add an extra note to the file name or something. Please! </p></blockquote>
<p>I said it <a href="http://www.adobeforums.com/webx?128@@.3c054206" title="Adobe Acrbat Macintosh Forum">here</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.lazydada.com/2007-11-10/illustrator-pdf-reply-on-adobe-forums/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->