🚀 go-pugleaf

This may be an old problem but I'm still fighting it. Checking AdobeForums again and again (just to make sure) did not turn up a solution.

Summary: whenever I use MS-Word to make a PDF file through Acrobat Distiller, "most" Type 1 fonts are converted into those pesky MSTT... approximations.

Environment: MS-Word 2000, Windows 98SE, Acrobat 3...then 4...now 5.0.5, Adobe PDFMaker 5.0, Adobe PS Driver 4.5.3 (007), ATM 4.1

Acrobat Distiller is the default printer (even when adding/removing fonts) and uses AdobePS 4.5.3

Made a document containing Type 1 fonts. Times, Helvetica, Symbol and Zapf Dingbats. Rendered into PDF using Distiller and various settings.

Constant ones: - Embed all fonts ON (Acrobat)
               - Always embed list = empty (Acrobat)
               - Never embed list = empty (Acrobat)
               - Don't use printer fnts OFF (PSCRIPT)
               - Send Type 1 as Native (PSCRIPT)
               - Send TT as Type 42 (PSCRIPT)
               - Threshold for bitmaps = 0 (PSCRIPT)

Variable ones: - Subset embedded fonts ON/OFF (Acrobat)
               - Substitute printer fonts for TT ON/OFF (PSCRIPT)

I know that there were substitution problems with the Base 14 Type 1 fonts inside Windows. But Symbol and Zapf always end up embedded in the PDF as original Type 1 fonts. Not so for Helvetica and Times.
OK so substitution won't work for these fonts, right?
But neither does it for stuff like Syntax, or AGaramond or AvantGarde or anything else I have. Always converted into MSTT... fonts

ATM.ini correctly lists all active Type 1 fonts. Initially WIN.ini did this as well, until I found out that AdobePS never looks in WIN.ini.

Usually I peek in the Acrobat Document Properties->Fonts dialog to check for any changes. In the beginning I checked the generated Postscript output as well, and from this I know that it must be the AdobePS driver that produces those MSTT... requests, and not Distiller (as far as I can see).

BTW I get the same results with AdobePS v4.50 (034), the one that comes with Acrobat 5.0.5 (I think). Printing directly to the Adobe Distiller printer (instead of using PDFMaker) doesn't make a difference either.

Finally, InDesign 2 and PageMaker work fine, probably because they contain PDF-generation code inside the program and do not use AdobePS to generate PDF files (my guess)

Any help or pointers to relevant information is appreciated.

Peter