Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

universal Filter May Produce Garbled Output when Spoolfile Originates from AdobeReader on Win 10 #621

Open
KurtPfeifle opened this issue Feb 17, 2025 · 0 comments

Comments

@KurtPfeifle
Copy link

KurtPfeifle commented Feb 17, 2025

d00264-002.txt

universal Filter (from cups-filter-core-drivers, v2.0.0-0ubuntu4) Produces Garbled Output when Spoolfile Originates from AdobeReader on Win 10

Problem Description

application//vnd.adobe-reader-postscript input for universal filter is mirrored and scaled down to less than 10% after being converted to PDF output. In the case of the provided example input it happens on page 1, while page 2 looks normal

Steps to reproduce the behavior:

  1. Take the attached file d00264-002.
  2. Run cupsfilter -p any-valid.ppd d00264-002 > universal-out.pdf
  3. Open universal-out.pdf in any PDF viewer of your choice
  4. Do you see any content on page 1? How does it compare to page 2?

Expected behavior

A clear and concise image of page content on page 1 similar to the one produced by gs -o ghostscript-out.pdf -sDEVICE=pdfwrite d00264-002

Screenshots

Screenshots from universal's output:

Image
Image 1: Page 1 output scaled down and horizontally mirrored.

Image
Image 2: Page 2 output seems to look normal. Here same zoom level for comparison.

Image
Image 3: Page 1 output by Ghostscript at 100% zoom level.

Image
Image 4: Page 2 output by Ghostscript at 100% zoom level.

System Information:

  • OS: [Ubuntu-24.04-LTS]

Additional context
The spoolfile was sent to me by a customer running Linux print servers with lots of different clients (Linux, Windows, macOS). It was retrieved as an example file exhibiting the same problem on various real-life printers.

It is not clear if AdobeReader is the only application which generates printer driver output leading to this problem.

Attachments:

How Ghostscript converted the spoolfile

d00264-002-processed-by-ghostscript.pdf

How universal converted the spoolfile

spoolfile-processed-by-universal-d00264-002.pdf

The original spoolfile (with an added .txt suffix)

d00264-002.txt
(.txt Suffix added by me, else it wouldn't upload. No suffix originally.)

More details to this bug report (f.e. output from manually run cupsfilter)

Issue-with-universal-Filter.pdf

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant