Article View: adobe.framemaker
Article #3055Re: One file not working, crashes FM
From: Art Campbell
Date: Tue, 13 Feb 2007 21:20
Date: Tue, 13 Feb 2007 21:20
5 lines
1462 bytes
1462 bytes
I don't have any way of knowing what fonts your translator has, but yes, when you open the .rtf in FM, it is "converted" to an FM file. All you need to do is save it as a Frame file. It's the standard way most shops convert their Word files to FM; unless you're doing something unique with your scripts, there isn't a reason to take the intermediate step of converting to a .MIF file. If, when you first opened it, you received a "missing font" message in the FM console, then you may have to reconcile fonts. But all other things being equal, there may not be a problem. However, because you can open the .rtf directly and successfully from FM, I think you demonstrated that your conversion process is likely to be the culprit, not FM.
Technical Details
Message-ID:
<3bc322ff.5@webcrossing.la2eafNXanI>Path:
arc1-ca.pugleaf.net!g2news2.google.com!news1.google.com!news4.google.com!border1.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!newspeer1.nwr.nac.net!newsfeed.freenet.de!news.germany.com!news.isoc.lu!webcrossingReferences:
<3bc322ff.-1@webcrossing.la2eafNXanI>Show Full Headers
Complete Article Headers
X-Google-Thread: fd315,c9943cbc57cf4b13 X-Google-Attributes: gidfd315,public X-Google-Language: ENGLISH,ASCII-7-bit From: "Art Campbell" <art.campbell@gmail.com> Path: arc1-ca.pugleaf.net!g2news2.google.com!news1.google.com!news4.google.com!border1.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!newspeer1.nwr.nac.net!newsfeed.freenet.de!news.germany.com!news.isoc.lu!webcrossing Newsgroups: adobe.framemaker Subject: Re: One file not working, crashes FM Message-ID: <3bc322ff.5@webcrossing.la2eafNXanI> Date: Tue, 13 Feb 2007 13:20:00 -0800 References: <3bc322ff.-1@webcrossing.la2eafNXanI> Lines: 14 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit