Re: Bug: FM Shadings Not Converting to Acrobat 4.05a

[Dan Emory <danemory@xxxxxxxxxxxx>]

At 01:52 PM 6/25/00 -0700, Dov Isaacs wrote:
>The problem is NOT directly FrameMaker. The problem appears to
>be a problem in the Distiller 4.05 which has been reported and
>is scheduled to be fixed in the next major release of Acrobat.
===========================================
The problem I've described, plus a number of others reported by Shlomo Perets,
would seem to warrant a downloadable fix well in advance of Acrobat 5, which
is likely to be a year or more away. I don't think we should have to pay an
upgrade price to fix a problem that's been there since Acrobat 2.
================================================
>NOTE: FrameMaker implements its shadings via patterns through
>GDI under Windows resulting in some rather unusual sequences through
>various drivers. The results of AdobePS 4.x, AdobePS 5.x, AdobePS 8.x
>are different from each other in terms of the type of PostScript
>generated for these patterns.
==========================================
It's not clear from the above whether the bug exists on all platforms,
or just Windows platforms. Is the problem on Windows platforms
being produced by the combination of AdobePS 4.1.3
AND Distiller 4.05, or is a fix required to Distiller alone?
=======================================
>At 6/25/00 11:30 AM, Dan Emory wrote:
> >Old Adobe bugs never die, they just shade away.
> >
> >On Windows 98SE, using FM V5.5.6, I create swatches of the seven FM 
> shading patterns made up of diagonal, horizontal, vertical, and 
> cross-hatched lines. Then, I print to a .ps file, using Adobe Postscript 
> Printer Driver 4.3.1 and the Distiller 4.05a PPD, specifying a resolution 
> of 2400. The Distiller job options are set up with no compression of 
> graphics, text, or line art. In the resulting PDF, all of the shaded 
> swatches are displayed and printed as pure white. In earlier versions of 
> Acrobat, they all appeared as the same shade of dark gray. A recent post 
> by Shlomo Perets indicates that the problem persists in FM 6.0.
> >
> >This problem has been with us since FM 5.1 and Acrobat 2 if I'm not 
> mistaken. Why hasn't it been fixed?

====================
| Nullius in Verba |
====================
Dan Emory, Dan Emory & Associates
FrameMaker/FrameMaker+SGML Document Design & Database Publishing
Voice/Fax: 949-722-8971 E-Mail: danemory@primenet.com
10044 Adams Ave. #208, Huntington Beach, CA 92646
---Subscribe to the "Free Framers" list by sending a message to
majordomo@omsys.com with "subscribe framers" (no quotes) in the body.



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