View Issue Details

IDProjectCategoryView StatusLast Update
0001011savapage-core[All Projects] Generalpublic2020-02-02 13:54
ReporterrijkrAssigned Torijkr 
PrioritynormalSeverityminorReproducibilitysometimes
Status closedResolutionfixed 
Product Version1.0.0 
Target Version1.1.0Fixed in Version1.1.0 
Summary0001011: Add PDF repair option for proxy printing
DescriptionIST: Uploaded PDF files (Web Print) might not have valid PDF format. These files don't get noticed, since they are shown correctly as SafePages. However, when these corrupted PDFs are proxy printed, CUPS filtering might deliver incorrect PDL (PostScript) so printed output will not be as expected (in some cases we saw just a blank page is printed).
SOLL: Add configuration item to enable/disable repair of any PDF just before sending it to CUPS: "proxy-print.repair.enable" Y | N (default). The repair is done with:
pdftocairo -pdf print.pdf print_repaired.pdf
The repair action only takes a few seconds, even for larger PDF files. https://superuser.com/questions/278562/how-can-i-fix-repair-a-corrupted-pdf-file : Ghostscript prepress is an alternative, but we found out that it does not repair in all cases:
gs -o repaired.pdf -sDEVICE=pdfwrite -dPDFSETTINGS=/prepress corrupted.pdf
Additional InformationUse `pdf2ps` on command line to check if PDF is corrupted. If corrupted, error messages will show on stdout. E.g.
**** Error reading a content stream. The page may be incomplete.
               Output may be incorrect.
TagsNo tags attached.

Relationships

related to 0001077 resolvedrijkr savapage-server Set strict defaults for Web Print PDF validation 
related to 0001029 closedrijkr savapage-core Add PDF repair option for Web Print 
related to 0001078 assignedrijkr savapage-core Remove deprecated proxy-print.repair.enable 

Activities

rijkr

2019-08-05 16:41

administrator   ~0000165

release 1.1.0

Issue History

Date Modified Username Field Change
2018-12-18 20:57 rijkr New Issue
2018-12-18 20:57 rijkr Status new => assigned
2018-12-18 20:57 rijkr Assigned To => rijkr
2018-12-18 21:02 rijkr Additional Information Updated View Revisions
2018-12-18 22:27 rijkr Status assigned => resolved
2018-12-18 22:27 rijkr Resolution open => fixed
2018-12-18 22:27 rijkr Fixed in Version => 1.1.0
2018-12-19 13:55 rijkr Description Updated View Revisions
2018-12-19 13:56 rijkr Additional Information Updated View Revisions
2018-12-28 15:32 rijkr Steps to Reproduce Updated View Revisions
2019-01-07 20:12 rijkr Steps to Reproduce Updated View Revisions
2019-01-29 17:08 rijkr Relationship added related to 0001029
2019-02-27 10:30 rijkr Description Updated View Revisions
2019-02-27 10:31 rijkr Description Updated View Revisions
2019-08-05 16:41 rijkr Status resolved => closed
2019-08-05 16:41 rijkr Note Added: 0000165
2019-09-03 09:44 rijkr Relationship added related to 0001078
2020-02-02 13:54 rijkr Relationship added related to 0001077