-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
pdf2printable default page size #25
Comments
What makes you expect that? Also note that there is no such thing as a "[single] page size as ... file" - each page can be different (MediaBox), and that's really quite bad for printing. |
Guilty as charged. You sure did.
It's hard to argue with this.
Yes, I did notice that when MediaBox can be parsed with
Haha. I, for one, like inches, teaspoons, and pounds for home and kitchen, kilograms and millimeters for the laboratory and hospital. But it's not hard to imagine how messy our system must seem to folks used to the simplicity of base10 everywhere. Listen, I could never print reliably from my GNU/Linux boxes to my wireless Brother printer using CUPS+driver (mostly because of computers periodically not being able to find the printer on the WLAN, despite it having a static ip address--go figure). Since switching to driverless printing powered by pdf2printable+ipptool back in September 2023, I've hit 100% reliability. Between my kids being homeschooled and my wife getting her Master's in the Great Books we do quite a bit of printing, so reliability is a must. I'm in your debt. Happy hacking! |
I can only recommend |
My current setup does involve tmp files and could be simpler. I'll get around to refactoring my shell script to use |
You do that in your time of course, but it should be a much better experience. |
Sorry to bother again. I noticed that pdf2printable defaults to A4 page size for output files. I was a surprised by that--I expected that if size is not specified, output file would have same page size as input file. What are your thoughts about this?
The text was updated successfully, but these errors were encountered: