You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we have Chromium routes for sources in HTML, Markdown and URLs:
Is there a way to have a PDF file as source?
It's useful for when you want to change it's PDF-A standard or simply by regenerating it to normalize/fix broken PDF.
Currently, PDF Engines endpoints have a route able to convert from source PDF file:
But it's simply not reliable as Chromium is. Tried some PDF files with EXIF pictures and it is breaking while trying to convert these attached pictures.
I would love to have the same behavior for Chromium.
The text was updated successfully, but these errors were encountered:
Chromium only handles HTML based inputs. When you ask to convert to a specific PDF/A format, it's actually the LibreOffice PDF engine that does the job. In other words, HTML into PDF via Chromium, and then PDF/A via LibreOffice. The PDF engines endpoint just skip the HTML part and calls LibreOffice directly.
@gulien got it, but Chrome browser is able to read PDFs and regenerate them by printing to PDF.
Aren't we able to have an API to print PDF from PDF file?
I tried LibreOffice PDF engine, but, as I said, I faced some errors logging something related to "EXIF" pictures converting (PDF attachments?).
Currently we have Chromium routes for sources in HTML, Markdown and URLs:
Is there a way to have a PDF file as source?
It's useful for when you want to change it's PDF-A standard or simply by regenerating it to normalize/fix broken PDF.
Currently, PDF Engines endpoints have a route able to convert from source PDF file:
But it's simply not reliable as Chromium is. Tried some PDF files with EXIF pictures and it is breaking while trying to convert these attached pictures.
I would love to have the same behavior for Chromium.
The text was updated successfully, but these errors were encountered: