[gs-bugs] [Bug 691636] New: pdf file with distiller security settings is rendered incorrectly by ghostscript

bugzilla-daemon at ghostscript.com bugzilla-daemon at ghostscript.com
Tue Sep 21 15:00:31 UTC 2010


http://bugs.ghostscript.com/show_bug.cgi?id=691636

           Summary: pdf file with distiller security settings is rendered
                    incorrectly by ghostscript
           Product: Ghostscript
           Version: other
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P4
         Component: PDF Interpreter
        AssignedTo: alex.cherepanov at artifex.com
        ReportedBy: heiko.honrath at gmx.de
         QAContact: gs-bugs at ghostscript.com
   Estimated Hours: 0.0


Created an attachment (id=6741)
 --> (http://bugs.ghostscript.com/attachment.cgi?id=6741)
A zip with all mentioned files.

A pdf file distilled with Distiller security settings is rendered incorrectly
by ghostscript.

The same file is rendered correctly when it is distilled without security.

I verified with Distiller 6.0.1 and Distiller 8.1.0 and with 128 bit and 40 bit
encryption.

I tested ghostscript 8.63, 8.70, 8.71 and 9.00 (all on Windows XP).

The secured pdf file is rendered correctly by Adobe Reader 8 and 9 and also by
SumatraPDF, Foxit Reader, Mupdf and PDF Xchange Viewer and even Evince and KDE
4/Okular (all on Windows XP).

The password for the secured pdf file is "secret" (without the double quotes).

Please see attached ZIP file with:

folder.joboptions            - Adobe Distiller settings

security_settings.png        - Adobe Distiller security settings

Stellenanzeige.ps            - the original PostScript file

Stellenanzeige_secured.pdf   - pdf file created by Distiller with security on

Stellenanzeige_secured.png   - how the pdf file is rendered

Stellenanzeige_unsecured.pdf - pdf file created by Distiller with security off

-- 
Configure bugmail: http://bugs.ghostscript.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the gs-bugs mailing list