Also you may want to try phantomJS-I haven't done that though. A difference between PhantomJS and wkhtmltopdf is that the latter is using X server to do its renderings, and this could of be the reason.1 answer Top answer: My solution was to migrate to wkhtmltopdf.It turns out that my problem happened under these circumstances: Always with PhantomJS With wkhtmltopdf.
UPDATE: Use font-manager by the author of pdfkit to substitute the font.
#Pdfkit vs phantomjs pdf#
I am trying to find a solution that lets render text in (almost) any language within a PDF using pdfkit, without having to write a sophisticated language recognition tool, which I feel would be an overkill.Īny thoughts and suggestions will be much appreciated. They are both headless scriptable browsers that make it relatively easy to get good looking results relatively quickly. I spotted this "google noto" open font which has it all, but the problem is that there is no single TTF file with all languages, and there can't be as font files are limited to 65K glyphs. But you can also look into using things like phantomjs (or a bit older wkhtmltopdf). I understood that I need to use the right font that should have proper characters included, as explained here. Headless Chrome seems also more stable in performance when running the benchmark again and seems to be the big winner here. it doesn't render correctly, and I have no means of knowing what language the comments will be coming in-in fact I am gathering them from around the world. As you can see, Headless Chrome finishes 55 faster while consuming 38 less memory than PhantomJS. It works really well, however now I spotted that when a comment is in Japanese, Chinese, Arabic, etc.
The PDFs contain people's comments coming from a remote source via an HTTP request. I am using pdfkit to dynamically generate PDF documents within a nodewebkit application.
0 kommentar(er)
