When converting images to PDF using PDF-Tools, the user has the option to set the width and height of the document pages in accordance with the original images (item "By Image — Select Paper Size by Image Size"). I assume that the image resolution is taken from their metadata, and for images that do not support DPI storage — the current display data.
However, a similar function is missing in PDF-XChange Standard, which requires specifying a fixed page size from among the standard or manually specified by the user. I suggest considering the possibility of saving web pages to PDF using the page width calculated from the page width in pixels and the display DPI (this data is available to the browser), and calculating the page height dynamically depending on the length of the web page. This will save web pages in a convenient form, as close as possible to the original view, without frequent page breaks. Also, I think it would be a better solution than manually gluing "standard" pages with cropped margins or saving long screenshots with subsequent recognition (and losing links).
As a preventive measure against exceeding the 15,000,000 inch limit, it would be possible to add forced splitting of pages exceeding this limit when saving to PDF 2.0 (or smaller, in cases of use when saving earlier versions of PDF or to ensure compatibility with older software).
[suggestion] Add "By web-page size" option to the "Paper size" list
Moderators: PDF-XChange Support, Daniel - PDF-XChange, Chris - PDF-XChange, Sean - PDF-XChange, Vasyl - PDF-XChange, Stefan - PDF-XChange
-
- User
- Posts: 584
- Joined: Mon Sep 13, 2021 8:12 am
-
- Site Admin
- Posts: 11060
- Joined: Wed Jan 03, 2018 6:52 pm
Re: [suggestion] Add "By web-page size" option to the "Paper size" list
Hello, Jensen Head
No promises, but I have passed it along for consideration.
[Edit]
Here is the reply I get form the dev team:
An effort was made to implement this in the past, as one of our Devs had the same idea you do. However, due to errors within the Chromium engine (which we make use of during our conversion), currently it is not possible to do so with an appropriate level of accuracy. Trying to offer this results in elements out of place, or some items entirely missing from the first page (and bumped down to the second page, if one exists.
As such, this request has been rejected for the time being. It will remain so until that engine sees the necessary improvements for us to perform these actions reliably, and as expected. For now, manual page definition is required.
Kind regards,
No promises, but I have passed it along for consideration.
[Edit]
Here is the reply I get form the dev team:
An effort was made to implement this in the past, as one of our Devs had the same idea you do. However, due to errors within the Chromium engine (which we make use of during our conversion), currently it is not possible to do so with an appropriate level of accuracy. Trying to offer this results in elements out of place, or some items entirely missing from the first page (and bumped down to the second page, if one exists.
As such, this request has been rejected for the time being. It will remain so until that engine sees the necessary improvements for us to perform these actions reliably, and as expected. For now, manual page definition is required.
Kind regards,
Dan McIntyre - Support Technician
PDF-XChange Co. LTD
+++++++++++++++++++++++++++++++++++
Our Web site domain and email address has changed as of 26/10/2023.
https://www.pdf-xchange.com
Support@pdf-xchange.com
PDF-XChange Co. LTD
+++++++++++++++++++++++++++++++++++
Our Web site domain and email address has changed as of 26/10/2023.
https://www.pdf-xchange.com
Support@pdf-xchange.com