Article View: adobe.framemaker
Article #2099Re: Framemaker PDF Import
From: Peter_Gold
Date: Thu, 09 Oct 2008 13:53
Date: Thu, 09 Oct 2008 13:53
16 lines
1387 bytes
1387 bytes
Hi, Jim: I've seen rtf conversions that fit your description perfectly. It's not caused by FM. but rather it's caused by the way the original source file was constructed - the one that was converted into the PDF from which you exported as rtf. The way the PDF interpreted the rtf also is part of the problem. I don't know if different FM releases convert from rtf with better or worse luck, but if you have earlier releases available, you could test the result. Another possibility is opening the rtf in Word or OpenOffice, re-saving as rtf, and importing the result into FM. Although rtf exports can retain format appearance and tag names, PDF only retains the appearance. HTH Regards, Peter Gold KnowHow ProServices
Technical Details
Message-ID:
<59b6b182.5@webcrossing.la2eafNXanI>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!news1.google.com!lightspeed.eweka.nl!81.171.88.16.MISMATCH!eweka.nl!hq-usenetpeers.eweka.nl!news4us.nl!webcrossingReferences:
<59b6b182.-1@webcrossing.la2eafNXanI>Show Full Headers
Complete Article Headers
X-Google-Thread: fd315,7c08e0bbb73c81dc X-Google-Attributes: gidfd315,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit From: Peter_Gold@adobeforums.com Newsgroups: adobe.framemaker Subject: Re: Framemaker PDF Import Message-ID: <59b6b182.5@webcrossing.la2eafNXanI> Date: Thu, 9 Oct 2008 06:53:13 -0700 References: <59b6b182.-1@webcrossing.la2eafNXanI> Lines: 23 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit Path: arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!news1.google.com!lightspeed.eweka.nl!81.171.88.16.MISMATCH!eweka.nl!hq-usenetpeers.eweka.nl!news4us.nl!webcrossing