Potential bug in PDFNet npm module

89 views
Skip to first unread message

Bala Abhinav Kirthy

unread,
May 28, 2020, 1:07:43 PM5/28/20
to PDFTron PDFNet SDK
Hi,

We have been evaluating pdfNet SDK (NodeJS/Linux-Debian) and We had encountered issues related to missing fonts as well as conversion of `umlauts` (German characters).
I am using the `Convert.officeToPdfWithPath` method to convert and I am using the setResourceDocPath method in the OfficeToPdfOptions constructor to provide a resource document embedded with multiple fonts. But, for some reason, the fonts are still not transcoded properly into the output PDF document.

I feel that this could be a potential bug with the npm module. I am also attaching a screenshot of the source code that I have written. Please advice.

Screenshot 2020-05-28 at 11.33.32 AM.png

Best.

Filestage Logo
phone +49 711 96589050
office Lautenschlagerstraße 16, 70173 Stuttgart, DE
Filestage GmbH, Amtsgericht Stuttgart: HRB 749557
Geschäftsführer: Niklas Dorn, Maël Frize, Simon Kontschak
LinkedIn Twitter Facebook
Working from home? We’ve created these resources for you:

Ryan

unread,
May 28, 2020, 5:02:34 PM5/28/20
to PDFTron PDFNet SDK
If you have not already you should try the latest SDK version here.

If that doesn't help then perhaps you need additional font coverage on your server, see this post below.

Supplemental reading:
Reply all
Reply to author
Forward
0 new messages