Article View: adobe.framemaker
Article #24660Re: Problem building a book
From: Tim Murray
Date: Wed, 28 Aug 2002 22:59
Date: Wed, 28 Aug 2002 22:59
3 lines
1343 bytes
1343 bytes
I just spent quite a while screwing around with a Word - to - PDF issue, where (1) plain Arial and Times New Roman caused Distiller to say that ArialMT and TimesNewRomanMT could not be found, even though Distiller knew explicitly where they were located; and (2) where Word let me use Arial and TNR even when they were both inactive but at long as ATM was running. Turns out that in my case, anyway, if Arial and TNR has to be loaded by ATM because they are not in the Fonts folder (I usually keep very little there), then the problem occured. But if I just place them in the Fonts folder, Word works okay.
Technical Details
Message-ID:
<1de54a39.4@WebX.la2eafNXanI>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!sn-xit-04!supernews.com!news.maxwell.syr.edu!newshosting.com!news-xfer1.atl.newshosting.com!uunet!dca.uu.net!news1.dpn.deere.com!WebXReferences:
<1de54a39.-1@WebX.la2eafNXanI>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fd315,92f904f25ec056a7,start X-Google-Attributes: gidfd315,public X-Google-ArrivalTime: 2002-08-29 00:00:26 PST From: "Tim Murray" <tlmurray@techknowledgecorp.com> Newsgroups: adobe.framemaker Subject: Re: Problem building a book Message-ID: <1de54a39.4@WebX.la2eafNXanI> Date: Wed, 28 Aug 2002 15:59:30 -0700 References: <1de54a39.-1@WebX.la2eafNXanI> Lines: 11 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!sn-xit-04!supernews.com!news.maxwell.syr.edu!newshosting.com!news-xfer1.atl.newshosting.com!uunet!dca.uu.net!news1.dpn.deere.com!WebX