🚀 go-pugleaf

I can only say that I used to suffer from this, and various
combinations of changing and reinstalling printer drivers eventually
seemed to make it go away.

Aandi Inston

One thing that you don't tell us is whether you actually have the Helvetica and Times Type 1 families installed via ATM on your system.

Let's assume that you do for the time being. The next question is whether you have ATM Lite 4.1 or ATM Deluxe 4.1. If you have ATM Lite 4.1, it is possible that if your copy was an "early" copy of ATM Lite 4.1, it is incompatible with the AdobePS 4.4.x and later (including the versions you have installed). Uninstall the current ATM Lite 4.1 you have and download the latest version (actually 4.1.1, but labelled as 4.1) and install it. Then try again.

- Dov

I do have these installed whenever necessary. One of the Adobe Technical Documents suggested to uninstall all fonts, all printer drivers, wipe clean win.ini and so on, and then reverse the process. By the second time I had to do this, I started throwing out all unneeded fonts and put the remainder in sets.

Currently I got two sets that I can turn on/off at will: Base 14 with the standard fonts that all PS printers carry, and a second one with some miscellaneous fonts (like AvantGarde, AGaramond etc.). In case I read your remark wrong: They're all installed via ATM because I don't know of any other methods of using Type 1 fonts on Win98SE (do you? maybe that would solve my problem...)

I don't have ATM Lite. I use ATM Deluxe because that's what I bought a long time ago. I did read your official alert on Planet PDF (dated May 9th, 2000) about AdobePS 4.4 problems and a subsequent fix that would be released. But I haven't found any updates for ATM Deluxe on Adobe's site (except for some fix that solves setup/registry problems). I don't like to drop software we put money in, but trying ATM Lite 4.1.1 anyway seems like my best chance to solve this. I'll keep you posted.

Thanks

Peter

Again no luck. Installing ATM Lite (version 4.1.2) instead of ATM Deluxe doesn't change a thing when I try to create a PDF file from MS-Word. All Type 1 fonts are still replaced by MSTT... substitutes except for T-1 Symbol and T-1 Zapf Dingbats. Weird.

Is there anything else I can try?

Peter

Try the suggestions in "UPDATE (2001-11-16) Windows 2000/XP Zapf Dingbats Display Problem". I do it as standard procedure for nearly every Windows machine I encounter.

Tim

The steps in "UPDATE (2001-11-16)..." weren't very useful, since I'm using a Win98SE machine = no BPD files and the problems I've got are the inverse of the one described in the Dov's Update.

But wait, your suggestion did give me an idea: what if only fonts listed in the PPD can be embedded in a Word-generated PDF file? It's just like that (see Adist5.ppd), Courier-Symbol-Zapf are just fine, the others get converted into MSTT... approximations. But I'm not there yet. Adding font specs to the PPD file isn't trivial. And even if the lines I add are syntactically correct, I'm still wondering whether I should also be deleting some sort of hidden font list (like the BPD files on Win2K). In short, tinkering with PPD specs isn't an improvement (yet).

Peter

No, if your system is properly configured, any font that doesn't specifically prohibit embedding (TrueType or OpenType with font embedding restrictions) should be embeddable without a problem, regardless of anything in the Acrobat Distiller PPD file. And, as you noted, my posting of 2001-11-16 is totally and utterly irrelevant to your case since you are running Windows'9x/Me.

If you are getting �MSTTxxxxxxx� fonts, it is indicative of some corruption in your registry and the inability of the operating system, ATM, and the PostScript driver (not PSCRIPT, use AdobePS) to communicate with each other. If you are using a printer driver instance created via the "Add New Printer" wizard using the PSCRIPT 4.0 driver, that would likely explain your problems.

- Dov