We are currently evaluating GemBox.Document. Overall we have been very pleased with the capabilities but we have encountered one issue which would currently prevent us from purchasing. Firstly a little context…
The system that we are building will fit into an existing set of services. The .net service will take letters and correspondence that will be sent to customers and manipulate the contents. Ultimately your library will produce a PDF file which can then go on for further processing (in this case by a service written in Node.js). The Node.js service applies a letterhead to the PDF and then sends a physical copy to the customer.
Anyway, we have found that one letter causes the upstream Node.js service to error because the library detects an incorrect header in the compression stream. Weirdly, this only happens when I apply my 30 day trial licence to GemBox.Document and the PDF can be processed when the free licence is in place). The PDF does, however, open in the browser/Acrobat.
I have a test bed that contains the letter, the .net code that calls GemBox.Document and a Typescript project that will generate the error. Is there somewhere that I can upload this code so it does not appear on this forum?
Steps to reproduce:
- Run the .net code. It will copy a DOCX file to the build directory. Once it runs the code will generate a PDF file called Incorrect.pdf in the build directory.
- Go to the nested Typescript project and run “npm install”. All libraries have been checked with Snyk.
- Then run “npx ts-node index.ts”. This will read the PDF directly from the .net build directory. It will attempt to add a letterhead to the file, but this will fail because the PDF is incorrectly formatted.