[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[New search]
To: russurquhart1@xxxxxxxxxxx, framers@xxxxxxxxx
Subject: Re: Windows Framemaker .ps file to Mac PDF file
From: "Fred Ridder" <docudoc@xxxxxxxxxxx>
Date: Tue, 11 Oct 2005 10:03:51 -0400
Delivered-to: jeremyg-freeframers:org-ffarchiv@freeframers.org
In-reply-to: <c7d9dd600510110502v670d54e0i175f394fb9e647d0@mail.gmail.com>
Sender: owner-framers@xxxxxxxxx
If you're going to distill a PostScript file on a system other than the one which generated the PostScript, it's essential to guarantee that all fonts used are included in the PostScript code. Normally, a Windows printer driver does not clutter the PS code with font information for any font that it knows is resident in the target printer. One of the reasons why you should always use the "Acrobat Distiller" or "Adobe PDF" printer driver (different names indicate drivers for different versions of Acrobat) on a Windows machine. That driver knows that the PS is intended for Distiller rather than a physical printer, and therefore knows that there are no resident fonts.
Additionally, the newer Adobe PDF printer driver has a special Printing Preferences property sheet that includes an option "Do not send fonts to Adobe PDF" (meaning the virtual printer). It's important to note that this option is *selected* by default because it is normally better/faster for Distiller to get the fonts it needs to embed directly from the font files rather than from the PS file; but that is only true when you're distilling on the same system that is generating the PS. If you're going to distill on a different machine, the "Do not send fonts" approach opens the door to all sorts of font availability/naming/ compatibility issues. It is very muchy safer to de-select the "Do not send fonts" option so that the PostScript file will be self-contained.
My opinion only; I don't speak for Intel Fred Ridder Intel Parsippany, NJ
From: Art Campbell <art.campbell@xxxxxxxxx> To: Russ Urquhart <russurquhart1@xxxxxxxxxxx> CC: Free Framers <framers@xxxxxxxxx> Subject: Re: Windows Framemaker .ps file to Mac PDF file Date: Tue, 11 Oct 2005 08:02:29 -0400
I'd second your guess that it is font incompatibility... Even though the fonts may be the same fonts, their names are likely to be handled differently in the two environments; font imcompatibility is always one of the big problems with moving files. As a test, maybe turn off "Embed Fonts" in Distiller to see if that helps.
Art
On 10/11/05, Russ Urquhart <russurquhart1@xxxxxxxxxxx> wrote: > Hi, > > I have a .ps file we created from Framemaker 7.0 that we need to have > as a pdf file. > > When we tried to distill the file to a pdf with Acrobat 7.0 on > windows, but the program just stopped. No log file no nothing. > > I took the .ps file home to my mac system and tried distilling it > with Acrobat 7.0 for mac OS x. It distills, but some of the font > encoding is incorrect. (I have the same fonts, and made sure that i > have chosen to embed those in the pdf.) > > It looks like that windows encodes to the .ps file different than the > Mac. > > Anyone have any ideas? > > Thanks > > Russ > > ** To unsubscribe, send a message to majordomo@xxxxxxxxx ** > ** with "unsubscribe framers" (no quotes) in the body. ** >
--
Art Campbell art.campbell@xxxxxxxxx
"... In my opinion, there's nothing in this world beats a '52 Vincent
and a redheaded girl." -- Richard Thompson
No disclaimers apply.
DoD 358
** To unsubscribe, send a message to majordomo@xxxxxxxxx ** ** with "unsubscribe framers" (no quotes) in the body. **
** To unsubscribe, send a message to majordomo@xxxxxxxxx ** ** with "unsubscribe framers" (no quotes) in the body. **