<?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: XMPIe &#8220;Missing Plug-In&#8221; Issue</title>
	<atom:link href="http://www.claudiamccue.com/2009/03/xmpie-missing-plug-in-issue/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.claudiamccue.com/2009/03/xmpie-missing-plug-in-issue/</link>
	<description>Graphic Arts Training for Professionals</description>
	<lastBuildDate>Tue, 07 Sep 2010 16:49:25 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tim Porath</title>
		<link>http://www.claudiamccue.com/2009/03/xmpie-missing-plug-in-issue/comment-page-1/#comment-246</link>
		<dc:creator>Tim Porath</dc:creator>
		<pubDate>Tue, 12 May 2009 14:00:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.claudiamccue.com/?p=460#comment-246</guid>
		<description>Hey, I&#039;ve been having the same problem. I was using XMPie and Darwin (trials) on my CS3 install, and when I moved to CS4 without those plugins it&#039;s given me a lot of grief. Since it seemed like exporting to .INX was the best solution I wrote a Javascript that automates most of the process. 
http://www.mediafire.com/download.php?zo3uqymwzwz
If anyone would like to help me test and improve it I would love it, it&#039;s working well for me on OS 10.5 but I&#039;d love to know if it works on PC as well
In short it -
1) Asks you to re-save the file (I recommend saving a copy since it will overwrite it during this process)
2) Exports to INX
3) Closes the document
4) Opens the INX version
5) Saves the INX version as an INDD file, overwriting the original with a new, plugin free file
Code is provided as is, so please be careful with it! I highly recommend using it on backups only!
The easiest way to install it is to go to Window/Automation/Scripts, right click on the User folder and Reveal in Finder. Then copy the file into the Scripts Panel folder, and you should see it
-Tim Porath
skooges@gmail.com</description>
		<content:encoded><![CDATA[<p>Hey, I&#8217;ve been having the same problem. I was using XMPie and Darwin (trials) on my CS3 install, and when I moved to CS4 without those plugins it&#8217;s given me a lot of grief. Since it seemed like exporting to .INX was the best solution I wrote a Javascript that automates most of the process.<br />
<a href="http://www.mediafire.com/download.php?zo3uqymwzwz" rel="nofollow">http://www.mediafire.com/download.php?zo3uqymwzwz</a><br />
If anyone would like to help me test and improve it I would love it, it&#8217;s working well for me on OS 10.5 but I&#8217;d love to know if it works on PC as well<br />
In short it -<br />
1) Asks you to re-save the file (I recommend saving a copy since it will overwrite it during this process)<br />
2) Exports to INX<br />
3) Closes the document<br />
4) Opens the INX version<br />
5) Saves the INX version as an INDD file, overwriting the original with a new, plugin free file<br />
Code is provided as is, so please be careful with it! I highly recommend using it on backups only!<br />
The easiest way to install it is to go to Window/Automation/Scripts, right click on the User folder and Reveal in Finder. Then copy the file into the Scripts Panel folder, and you should see it<br />
-Tim Porath<br />
<a href="mailto:skooges@gmail.com">skooges@gmail.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philip Haxo</title>
		<link>http://www.claudiamccue.com/2009/03/xmpie-missing-plug-in-issue/comment-page-1/#comment-245</link>
		<dc:creator>Philip Haxo</dc:creator>
		<pubDate>Mon, 04 May 2009 16:56:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.claudiamccue.com/?p=460#comment-245</guid>
		<description>We have had the same issue. The easiest way to strip that content (assuming you aren&#039;t going to make edits and resubmit the file for additional variable content using XMPie) is to export it as an INX file. When you open the file back up in inDesign it will no longer contain the XMPie tagging, and won&#039;t prompt for the missing plugin.</description>
		<content:encoded><![CDATA[<p>We have had the same issue. The easiest way to strip that content (assuming you aren&#8217;t going to make edits and resubmit the file for additional variable content using XMPie) is to export it as an INX file. When you open the file back up in inDesign it will no longer contain the XMPie tagging, and won&#8217;t prompt for the missing plugin.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Baldaro</title>
		<link>http://www.claudiamccue.com/2009/03/xmpie-missing-plug-in-issue/comment-page-1/#comment-232</link>
		<dc:creator>David Baldaro</dc:creator>
		<pubDate>Wed, 25 Mar 2009 14:52:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.claudiamccue.com/?p=460#comment-232</guid>
		<description>Folks, I&#039;ve been chatting with the R&amp;D team on this issue. For all the details check out my blog, http://david.baldaro.me.uk/2009/03/xmpie-and-the-missing-plug-in-issue/</description>
		<content:encoded><![CDATA[<p>Folks, I&#8217;ve been chatting with the R&amp;D team on this issue. For all the details check out my blog, <a href="http://david.baldaro.me.uk/2009/03/xmpie-and-the-missing-plug-in-issue/" rel="nofollow">http://david.baldaro.me.uk/2009/03/xmpie-and-the-missing-plug-in-issue/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Claudia</title>
		<link>http://www.claudiamccue.com/2009/03/xmpie-missing-plug-in-issue/comment-page-1/#comment-229</link>
		<dc:creator>Claudia</dc:creator>
		<pubDate>Thu, 19 Mar 2009 21:39:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.claudiamccue.com/?p=460#comment-229</guid>
		<description>The option to remove missing plug-in gunk was last seen in CS(1) as far as I can determine from a couple of quick experiments with older versions of InDesign. Apparently it&#039;s time to bring that back!</description>
		<content:encoded><![CDATA[<p>The option to remove missing plug-in gunk was last seen in CS(1) as far as I can determine from a couple of quick experiments with older versions of InDesign. Apparently it&#8217;s time to bring that back!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen B</title>
		<link>http://www.claudiamccue.com/2009/03/xmpie-missing-plug-in-issue/comment-page-1/#comment-228</link>
		<dc:creator>Stephen B</dc:creator>
		<pubDate>Thu, 19 Mar 2009 19:30:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.claudiamccue.com/?p=460#comment-228</guid>
		<description>I&#039;m still on CS3 and would be remaining, but a new project is forcing us to upgrade. I also noticed that some boxes that were &quot;unassigned&quot; were converted to text boxes. 

CS 4 should be here soon. If I have time I&#039;ll try the IDML export. 

I never noticed the &quot;remove missing plugin&quot; feature, but I would say that xmpie is at fault here.</description>
		<content:encoded><![CDATA[<p>I&#8217;m still on CS3 and would be remaining, but a new project is forcing us to upgrade. I also noticed that some boxes that were &#8220;unassigned&#8221; were converted to text boxes. </p>
<p>CS 4 should be here soon. If I have time I&#8217;ll try the IDML export. </p>
<p>I never noticed the &#8220;remove missing plugin&#8221; feature, but I would say that xmpie is at fault here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Claudia</title>
		<link>http://www.claudiamccue.com/2009/03/xmpie-missing-plug-in-issue/comment-page-1/#comment-226</link>
		<dc:creator>Claudia</dc:creator>
		<pubDate>Tue, 17 Mar 2009 15:56:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.claudiamccue.com/?p=460#comment-226</guid>
		<description>Timothy,
Thank you for your comment. My understanding is that IDML will be the &quot;transporter&quot; format going forward, used both for backsaving and for repurposing InDesign content for other uses. I&#039;ll be interested to hear whether IDML solves the text frame inset issue; if it does, I&#039;ll recommend that to other users who are going through this.

Of course, this isn&#039;t available to users of CS3...</description>
		<content:encoded><![CDATA[<p>Timothy,<br />
Thank you for your comment. My understanding is that IDML will be the &#8220;transporter&#8221; format going forward, used both for backsaving and for repurposing InDesign content for other uses. I&#8217;ll be interested to hear whether IDML solves the text frame inset issue; if it does, I&#8217;ll recommend that to other users who are going through this.</p>
<p>Of course, this isn&#8217;t available to users of CS3&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Timothy Perrett</title>
		<link>http://www.claudiamccue.com/2009/03/xmpie-missing-plug-in-issue/comment-page-1/#comment-225</link>
		<dc:creator>Timothy Perrett</dc:creator>
		<pubDate>Tue, 17 Mar 2009 12:55:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.claudiamccue.com/?p=460#comment-225</guid>
		<description>Claudia,

You are correct in saying that users of CS4 should export to IDML - doing this will ensure that there layout is safe from modification. Comparatively, INX was an internal Adobe format that was designed to make documents backward compatible with previous versions of InDesign - hence, not all layout options being supported in the format... INX was never intended to be full proof. 

Im sure their used to be an option in CS1 or CS2 to &quot;remove missing plugin data&quot; - oddly, that now appears to be missing from CS3 + CS4.

Timothy.</description>
		<content:encoded><![CDATA[<p>Claudia,</p>
<p>You are correct in saying that users of CS4 should export to IDML &#8211; doing this will ensure that there layout is safe from modification. Comparatively, INX was an internal Adobe format that was designed to make documents backward compatible with previous versions of InDesign &#8211; hence, not all layout options being supported in the format&#8230; INX was never intended to be full proof. </p>
<p>Im sure their used to be an option in CS1 or CS2 to &#8220;remove missing plugin data&#8221; &#8211; oddly, that now appears to be missing from CS3 + CS4.</p>
<p>Timothy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Claudia</title>
		<link>http://www.claudiamccue.com/2009/03/xmpie-missing-plug-in-issue/comment-page-1/#comment-224</link>
		<dc:creator>Claudia</dc:creator>
		<pubDate>Tue, 17 Mar 2009 11:30:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.claudiamccue.com/?p=460#comment-224</guid>
		<description>Anna,
If you export to InDesign Interchange, then open the Interchange (*.inx) file, that should remove the XMPie &quot;poison.&quot; I should caution you that one other commenter has said that doing this changed the text inset on some text frames. I haven&#039;t seen this happen, but it&#039;s worth mentioning.

And if you&#039;re in CS4 and you experience that text inset issue, maybe try exporting to InDesign Markup (idml), and open that back up.

Please keep me posted</description>
		<content:encoded><![CDATA[<p>Anna,<br />
If you export to InDesign Interchange, then open the Interchange (*.inx) file, that should remove the XMPie &#8220;poison.&#8221; I should caution you that one other commenter has said that doing this changed the text inset on some text frames. I haven&#8217;t seen this happen, but it&#8217;s worth mentioning.</p>
<p>And if you&#8217;re in CS4 and you experience that text inset issue, maybe try exporting to InDesign Markup (idml), and open that back up.</p>
<p>Please keep me posted</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anna</title>
		<link>http://www.claudiamccue.com/2009/03/xmpie-missing-plug-in-issue/comment-page-1/#comment-223</link>
		<dc:creator>Anna</dc:creator>
		<pubDate>Tue, 17 Mar 2009 09:11:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.claudiamccue.com/?p=460#comment-223</guid>
		<description>Interesting to see others with the same problems as I have.
My former colleague had xmpie installed on his computer, and even though he rarely used it, all files are now &quot;infected&quot; with the plugin.
I cannot open up a single file without indesign complaining about the missing plugin. The most annoying part is that I no longer can package my files.
I could install xmpie on my computer too. But then will everyone else down the line have the same problem as I. Does anyone know how to repair the files?

Br,
Anna</description>
		<content:encoded><![CDATA[<p>Interesting to see others with the same problems as I have.<br />
My former colleague had xmpie installed on his computer, and even though he rarely used it, all files are now &#8220;infected&#8221; with the plugin.<br />
I cannot open up a single file without indesign complaining about the missing plugin. The most annoying part is that I no longer can package my files.<br />
I could install xmpie on my computer too. But then will everyone else down the line have the same problem as I. Does anyone know how to repair the files?</p>
<p>Br,<br />
Anna</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Claudia</title>
		<link>http://www.claudiamccue.com/2009/03/xmpie-missing-plug-in-issue/comment-page-1/#comment-222</link>
		<dc:creator>Claudia</dc:creator>
		<pubDate>Mon, 16 Mar 2009 17:48:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.claudiamccue.com/?p=460#comment-222</guid>
		<description>Stephen,
Are you using CS3 or CS4? If you&#039;re using CS4, I&#039;d be interested to see if exporting to InDesign Markup (IDML) would provide a more faithful round-trip. (IDML isn&#039;t available in CS3.)

What does the printer say about their handling of the file? Can they guarantee that they didn&#039;t put any personalization in the file? I&#039;m curious because my customer&#039;s file (which inspired this saga) shouldn&#039;t have had any variable data in it, either. And my own few experiments led me to believe that simply opening, modifying, and resaving didn&#039;t introduce the packaging problem.

This has turned into much more excitement than I&#039;d anticipated... let me know what you hear from the printer.</description>
		<content:encoded><![CDATA[<p>Stephen,<br />
Are you using CS3 or CS4? If you&#8217;re using CS4, I&#8217;d be interested to see if exporting to InDesign Markup (IDML) would provide a more faithful round-trip. (IDML isn&#8217;t available in CS3.)</p>
<p>What does the printer say about their handling of the file? Can they guarantee that they didn&#8217;t put any personalization in the file? I&#8217;m curious because my customer&#8217;s file (which inspired this saga) shouldn&#8217;t have had any variable data in it, either. And my own few experiments led me to believe that simply opening, modifying, and resaving didn&#8217;t introduce the packaging problem.</p>
<p>This has turned into much more excitement than I&#8217;d anticipated&#8230; let me know what you hear from the printer.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
