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

qpdf-convert uses default (low) resolution #2812

Open
tasket opened this Issue May 16, 2017 · 2 comments

Comments

Projects
None yet
3 participants
@tasket

tasket commented May 16, 2017

Qubes OS version (e.g., R3.2):

R3.2

Affected TemplateVMs (e.g., fedora-23, if applicable):

all


Expected behavior:

Sanitized document that is suitable for presentation in a professional setting. Generally this means around 300 ppi and greater.

Actual behavior:

Conversion script uses pdftocairo default of 150 ppi, which can imapact readability and leave a poor impression.

General notes:

Balancing quality with the increase in file size is no doubt important, however given the capacities of modern machines it may be better to use 300 ppi as a default for Qubes and allow the user to specify a different resolution on the command line.

Discussion is here:
https://groups.google.com/d/msgid/qubes-users/20170515224610.GA3920%40Personal-Email


Related issues:

@tasket tasket closed this May 16, 2017

@SamuelHentschel

This comment has been minimized.

Show comment
Hide comment
@SamuelHentschel

SamuelHentschel May 16, 2017

tasket, why did you close this?

tasket, why did you close this?

@tasket

This comment has been minimized.

Show comment
Hide comment
@tasket

tasket May 16, 2017

@SamuelHentschel I must have hit the wrong button. Thanks for mentioning it!

tasket commented May 16, 2017

@SamuelHentschel I must have hit the wrong button. Thanks for mentioning it!

@tasket tasket reopened this May 16, 2017

@andrewdavidwong andrewdavidwong added this to the Release 4.0 milestone May 17, 2017

@andrewdavidwong andrewdavidwong added C: other and removed C: core labels May 17, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment