Summary: | Regression: pngmono thresholds rather than halftone above 150 dpi | ||
---|---|---|---|
Product: | Ghostscript | Reporter: | James Cloos <cloos> |
Component: | Other Driver | Assignee: | Chris Liddell (chrisl) <chris.liddell> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | P4 | ||
Version: | master | ||
Hardware: | PC | ||
OS: | Linux | ||
Customer: | Word Size: | --- | |
Attachments: | Make pngmono halftone rather than threshold |
Description
James Cloos
2014-03-01 17:13:22 UTC
This is a bug. Both the pngmono and pngmonod devices halftone, the difference is that the pngmono device uses an ordered halftone vs. an error diffusion dither for pngmonod. And in fact the pngmono device works as intended for lower resolutions (i.e. -r100). The cutoff appears to be 150 DPI, below that the output is correct, at or above it's not. Also, it's a regression, before 10de1e0bf9f3abd9c74401258388067c6e2ec36f all resolutions worked correctly. Yes, commit 10de1e0bf9f3abd9c74401258388067c6e2ec36f is the one which added the line: 3, 4, 1, 1, 2, 2, png_print_page), Which seems to be a cut-n-paste error from the png16 device. The patch looks fine, committed: http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=685e801f Thanks, and sorry for the mistake. |