-
Notifications
You must be signed in to change notification settings - Fork 254
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
[BUG] PDF Creation not working as expected #536
Comments
Welcome! Thanks for posting your first issue. The way things work here is that while customer issues are prioritized, other issues go into our backlog where they are assessed and fitted into the roadmap when suitable. If you need to get this done, consider buying a license which also enables you to use it in your commercial products. More information can be found on https://unidoc.io/ |
Hi @hjo33, Currently we are working to improve the DOCX to PDF conversion, however we still need to works on the Here's the current results we got so far when convert |
Heyho @sampila, we became aware of unioffice release 1.29.1 with the "DOCX to PDF image position overlapped with text" fix. Thanks and have a good Day! |
Hey @sampila, The generated files we're opened with chromium Version 126.0.6478.114 (Official Build) snap (64-bit) The code we use to fill and generate the pdf is the following:
PDF generation:
Versions are: If you need more infos or details don't hesitate to ask. |
Hi @TheGoderGuy, Yes we can confirm the issue on chrome or chromium for the pdf results, but we use adobe acrobat to visually verify the results. We will try to find out what's causing issue when viewed on chrome or chromium pdf. Here's the results on adobe acrobat example_libre.pdf and example_unidoc.pdf almost identical. |
@sampila Thank you for clarifying - our customers mostly use chrome, so the solace of having nearly identical display in Adobe is nice to know, but not relevant to achieve customer satisfaction on our side. |
Hi @martint17r Yes, our team currently investigate this issue, we would like to achieve same results on pdf web viewer also. |
Description
My team and I use a commercial unidoc/unipdf license. We use it to replace certain merge fields in a word document from a json body. Additionally we add a barcode or qrcode to the document. This works as expected and the data is added to the word document.
However if we want to generate a pdf from the given word document the rendering is completly thrown off. Converting the word document to pdf with libreoffice --headless gives the expected outcome.
Pictures and tables are also not rendered correctly and the barcode/qrcode is missing.
Expected Behavior
Expected the created pdf look similar to the one created by libreoffice
Actual Behavior
Steps to reproduce the behavior:
(_egac *Document )MailMerge
(_bddd *Document )SaveToFile
ConvertToPdf (d *_g .Document )
Attachments
Word template:
example_template.docx
Generated Unipdf:
PDF_unidpdf.pdf
Generated PDF with libreoffice
PDF_libreoffice.pdf
The text was updated successfully, but these errors were encountered: