Re: [Fwd: UPDATE (2001-11-15) Windows 2000/XP Zapf Dingbats Display Problem]

[Dov Isaacs <isaacs@xxxxxxxxx>]

Possibly yes and possibly the same solution will fix the problem
although the directory of the .PPD and .SPD files would be different.

I do not have any Windows NT 4 systems to test with and personally
do not consider NT 4 a system worth spending any time with since
there are so many problems in using Type 1 fonts and PostScript in
that environment -- it is Type 1 fonts and PostScript brain-dead!
It is so much so that I would most highly recommend that you move
on to Windows 2000 or Windows XP Professional if at all possible!

        - Dov


At 7/15/2002 08:12 PM, Huntley Eshenroder wrote:
>Hi,
>
>Sorry to raise the spectre of problems long forgotten, but I ran into a similar problem on WinNT 4.0, Frame 7, Acrobat 5. In my case, the Zapf Dingbat font did not appear in the Postscript file and hence, did not display in the resulting PDF.
>
>I realize that Win2K and XP both have NT at the core, but I'm not familiar enough with the internals to know if *should* be encountering this error on NT as well.
>
>Thanks,
>-Huntley
>
>-------- Original Message --------
>Subject: UPDATE (2001-11-15) Windows 2000/XP Zapf Dingbats Display  Problem
>Date: Thu, 15 Nov 2001 11:10:53 -0800
>From: Dov Isaacs <isaacs@Adobe.COM>
>To: (Recipient list suppressed)
>
>This is going out to a number of lists. My apologies if you receive it
>multiple times as a result of this form of distribution. If you are
>solely a Macintosh user and/or don't need to deal with problems associated
>with PostScript and PDF workflows originating from Windows-based systems,
>you can safely delete this message now ...


** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **