Bug 1541358

Summary: [RFE] Evince does not read PDF file PrintScaling scaling tags
Product: Red Hat Enterprise Linux 7 Reporter: Mikel Olasagasti <molasaga>
Component: evinceAssignee: Marek Kašík <mkasik>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.7CC: bgollahe, crungeho, jbastian, jeischma, mkasik, molasaga, toneata, tpelka, vbudikov
Target Milestone: rcKeywords: FutureFeature
Target Release: 7.7   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: evince-3.28.2-8.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-06 12:03:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1656436    
Attachments:
Description Flags
PDF for testing of PrintScaling (set to None)
none
PDF for testing of PrintScaling (set to AppDefault) none

Description Mikel Olasagasti 2018-02-02 11:27:45 UTC
1. Proposed title of this feature request
Adobe PDF file autofit label feature for Evince

3. What is the nature and description of the request?
We request that when Evince reads a PDF file that includes internal labels [1] it has to respect the printing labels as Adobe indicates [2], it sets up "temporally" the printer config to follow the label setup like Acrobat Reader does and prints the document properly. Once the program is closed and opened again or a different file is opened, Evince keeps its original printing configuration.

4. Why does the customer need this? (List the business requirements here)
Customer needs Evince to print the PDF as it's configured internally in the file, without the user modifying the printer setup every time they need to print a different document [3] (we are speaking about how to avoid teaching more than 3000 people how to modify printing setup before printing and rollout the config after the document was printed depending of the type of document).

5. How would the customer like to achieve this? (List the functional requirements here)
Evince needs to set up the printing configuration (page not autoscaled if the internal label of the document says so) if the pdf file indicates so. And that setup has to be temporal, just for printing that document, if I close Evince and open it again, the original set up has to come up. Right now Evince keeps saved the printing configuration if the user modifies it anytime.

6. For each functional requirement listed in question 5, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
We had provided documents prepared with the internal label to test if the application prints it properly. We can help doing the test in customer installations printing different documents with early Evince releases.

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
I don't think so.

8. Does the customer have any specific timeline dependencies?
We are coming from case #01943425 opened on Oct 02 2017, we would like to have this feature ASAP.

10. List any affected packages or components.
evince-3.22.1-7.el7.x86_64.rpm 
evince-libs-3.22.1-7.el7.x86_64.rpm 
evince-nautilus-3.22.1-7.el7.x86_64.rpm
gtk3-devel-docs-3.22.10-5.0.1.el7.x86_64.rpm
gtk3-3.22.10-5.0.1.el7.x86_64.rpm
gtk3-tests-3.22.10-5.0.1.el7.x86_64.rpm
gtk3-immodule-xim-3.22.10-5.0.1.el7.x86_64.rpm
gtk-update-icon-cache-3.22.10-5.0.1.el7.x86_64.rpm
gtk3-devel-3.22.10-5.0.1.el7.x86_64.rpm
gtk3-immodules-3.22.10-5.0.1.el7.x86_64.rpm
gtk3-debuginfo-3.22.10-5.0.1.el7.x86_64.rpm

11. Would the customer be able to assist in testing this functionality if implemented?
Yes, sure.

[1]   <</Type/Catalog/Pages 3 0 R/Outlines 4 0 R/ViewerPreferences<</PrintScaling/None>>>>
[2] https://www.adobe.com/content/dam/acom/en/devnet/pdf/pdfs/PDF32000_2008.pdf
[3] the common documents they are printing are: contracts (fitted/autoscale to page), labels for products in pre-cutted paper, standar notes to place in doors or desks, etc.

Comment 11 Marek Kašík 2019-05-03 09:15:49 UTC
Created attachment 1562262 [details]
PDF for testing of PrintScaling (set to None)

Evince should show "None" in "Page Scaling" setting in "Page Handling" tab in print dialog every time you open this PDF. You can change it but the default should be "None" there.

Comment 12 Marek Kašík 2019-05-03 09:23:02 UTC
Created attachment 1562263 [details]
PDF for testing of PrintScaling (set to AppDefault)

Evince should show default value of "Page Scaling" setting in "Page Handling" tab in print dialog when you open this PDF. The default is "Shrink to Printable Area" for first-time opened PDFs. It can be different for files which were already opened before since evince stores this information. The stored value is listed in "gio info the-pdf-file.pdf"

Comment 13 Marek Kašík 2019-05-06 10:27:07 UTC
(In reply to Marek Kašík from comment #12)
> Created attachment 1562263 [details]
> PDF for testing of PrintScaling (set to AppDefault)
> 
> Evince should show default value of "Page Scaling" setting in "Page
> Handling" tab in print dialog when you open this PDF. The default is "Shrink
> to Printable Area" for first-time opened PDFs. It can be different for files
> which were already opened before since evince stores this information. The
> stored value is listed in "gio info the-pdf-file.pdf"

This is wrong, the value of "Page Scaling" is stored globally for all documents in "~/.config/evince/print-settings" and not per document. So the "default" value should be the value which was used last for printing. The value "Shrink to Printable Area" is default only when you print from Evince for the first time.

Comment 19 errata-xmlrpc 2019-08-06 12:03:05 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:2022