Article View: adobe.framemaker
Article #1152Re: Filter error when importing graphic by reference
From: Art Campbell
Date: Wed, 31 Dec 2008 17:46
Date: Wed, 31 Dec 2008 17:46
9 lines
1270 bytes
1270 bytes
I perform the same operation all the time, without problems. Capture in SnagIt, save as PNG, import by ref, and then update the graphic. To fist this, first, I'd save the file out as MIF and reopen it and save it because the fact that you can't import anything would make me suspect that it's corrupted. There aren't any numeric limitations in FM, but you may be bumping into a RAM, network time, or swap space problem. Why don't you try saving the single massive (MIF-washed) file out into three or four component parts and see if that helps? Shouldn't make any difference in the book file at all, and it would certainly lessen the load on the system. Art
Technical Details
Message-ID:
<59b6e6b4.3@webcrossing.la2eafNXanI>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!newshub.sdsu.edu!webcrossingReferences:
<59b6e6b4.-1@webcrossing.la2eafNXanI>Show Full Headers
Complete Article Headers
X-Google-Thread: fd315,c3e47d66c046a18 X-Google-Attributes: gidfd315,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit From: "Art Campbell" <art.campbell@gmail.com> Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!newshub.sdsu.edu!webcrossing Newsgroups: adobe.framemaker Subject: Re: Filter error when importing graphic by reference Message-ID: <59b6e6b4.3@webcrossing.la2eafNXanI> Date: Wed, 31 Dec 2008 09:46:37 -0800 References: <59b6e6b4.-1@webcrossing.la2eafNXanI> Lines: 16 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit