Article View: adobe.framemaker
Article #24427Re: Getting an new font to work in Frame/PDF
From: Earl Boebert
Date: Mon, 21 Oct 2002 14:59
Date: Mon, 21 Oct 2002 14:59
76 lines
2665 bytes
2665 bytes
Well, now I don't know whether the font installed or not. Evidence that it did: 1. I am runnning Distiller 3.02 2. Acrobat Distiller->Font Locations reports the following: Macintosh HD: Adobe Acrobat 3.0: Fonts Macintosh HD: Adobe Acrobat 3.0: psdisk:fonts Macintosh HD: System Folder: Macintosh HD: System Folder: Extensions Macintosh HD: System Folder: Fonts 3. Creation/Modified Dates on the Parisian fonts in the Fonts folder are: Created: Mon, April 16, 1990, 11:44 AM Modified: Sat: Oct 19, 2002, 4:45 PM The latter is the date and time of the (apparently successful) download. Fonts are 4055 bytes long. No version data is reported. 4. Checking my account I get: �Download already pending.� Whatever that means. Launching the Adobe Dowload Manager gets: �There are no filtes to download at this time." Evidence that I didn't get it: Test file has one line of Parisian, one line of Lydian MT. Distiller -> Job Options -> Font Embedding has: Embed all fonts checked Parisian added to the �Always Embed� list Lydian goes, Parisian fails. Using Acrobat Reader 4.0. File->Document Info->Fonts reports: Original: Parisian Type: Type 1 Encoding: Custom Used:Adobe Sans MM Type: Type 1 and Original: LydianMT Type: Type 1 Encoding: Custom Used: Embedded Subset Type: Type 1 The fragments of the .ps file containing �parisian� are: %%DocumentFonts: Parisian LydianMT %%DocumentNeededFonts: Parisian %%DocumentSuppliedFonts: LydianMT and %%IncludeFont: Parisian /f44/Parisian :mre /f57 f44 18 scf %RBIBeginFontRasterizer: TrueType %%BeginFile: lw8_TrueType-2.0 The latter suggests that Frame is finding the old True Type font, which contradicts the date/time modified data on the font files. This is really reaching the "Why me, Oh Lord" stage :-) Cheers, Earl
Technical Details
Message-ID:
<1de63b5d.4@WebX.la2eafNXanI>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-05!sn-xit-06!sn-xit-08!supernews.com!newsfeed.news2me.com!opentransit.net!fr.clara.net!heighliner.fr.clara.net!newsfeed01.sul.t-online.de!t-online.de!WebXReferences:
<1de63b5d.-1@WebX.la2eafNXanI>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII X-Google-Thread: fd315,3a689fde88f99e1a X-Google-Attributes: gidfd315,public X-Google-ArrivalTime: 2002-10-21 09:00:00 PST From: "Earl Boebert" <boebert@swcp.com> Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-05!sn-xit-06!sn-xit-08!supernews.com!newsfeed.news2me.com!opentransit.net!fr.clara.net!heighliner.fr.clara.net!newsfeed01.sul.t-online.de!t-online.de!WebX Newsgroups: adobe.framemaker Subject: Re: Getting an new font to work in Frame/PDF Message-ID: <1de63b5d.4@WebX.la2eafNXanI> Date: Mon, 21 Oct 2002 07:59:45 -0700 References: <1de63b5d.-1@WebX.la2eafNXanI> Lines: 80 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit