If you check the attached Aspose generated PDF, you’ll notice that page 145 is missing. Oddly, the images for page 145 is on page 146. The Word file contains the proper pagination and formatting.
We are currently running Aspose.Words for NET 10.6
If you check the attached Aspose generated PDF, you’ll notice that page 145 is missing. Oddly, the images for page 145 is on page 146. The Word file contains the proper pagination and formatting.
We are currently running Aspose.Words for NET 10.6
Hi Nick,
Thanks for your inquiry. I observed the following error message when opening your la_traverse_du_Saguenaya.doc document with MS Word:
``
Could you please double check if the attached Word document is actually not corrupted on your side? I will investigate the issue further once I receive a valid document.
Best Regards,
Hi Awais,
There may have been an issue copying to dropbox. Please try the attached link.
Thanks!
Hi Nick,
Thanks for the inquiry.
We release a new version of Aspose.Words every month. Each new release contains many improvements, bug fixes and new features. So, we suggest you always use latest version of Aspose.Words. Moreover, I did not observe this problem with latest version. Could you please try it with latest version and let us know how it goes on your side?
Hello, in our testing of the recent trial version, we are also experiencing the missing pages. Please check attachments for the test file (6MB MS Word file, 232 pages long) and the generated PDF file by Aspose.
We are generating the conversion in a multithreaded implementation so it can be more scalable. The following are our test runs:
Conversion of 1 file: 40 seconds
Conversion of 3 files in parallel: 90 seconds
Conversion of 6 files in parallel: 480 seconds
Please kindly advise why Aspose is not scaling as expected? Thanks!
Hi
Brian,
Thanks for your inquiry.
Please note that Aspose.Words layout engine tries to mimic the way the Microsoft Word’s page layout engine works. To you, this means that if you convert a Microsoft Word document into PDF using Aspose.Words, the output will appear almost exactly as if it was done by Microsoft Word.
Secondly, I have noticed that MS WORD took 22 seconds when converting 6MB.doc to PDF on my side. On the other hand, when using the latest version of Aspose.Words i.e. 11.5.0, the average execution time the Save method took for three test runs was 32 seconds (this is because, on average, Aspose.Words layouts 10 pages per second).
Moreover, if you compare DOC and PDF documents page by page, you will see that documents are identical. No content is being lost.
Best Regards,
Hi Awais,
Thanks for your response. However, we are more concerned on the scalability of the solution using multi-threaded parallel runs. Although it only takes 32 seconds to convert our 6MB file to PDF, how long did it take you to run 6 parallel threads each converting the file at the same time?
Also, do you mean that I should just download the latest Aspose version and I will no longer be having the missing page problem? I already tested using 11.5.0 from https://releases.aspose.com/words/java and I still found the missing pages.
Regards,
Brian
Hi Brian,
Thanks for your inquiry.
Please note that Aspose components are designed to be simultaneously used by hundreds and thousands of users, for example in web applications. Aspose.Words does support multi-threading; however, the only thing you need to make sure is that you always use separate Document instances per each thread i.e. one thread should use one Document object. Unfortunately, it’s hard to quantify the CPU usage, as it depends on many factors. In Aspose.Words most likely you will see a spike in CPU usage when rendering (as the page layout is being updated) which will then quickly level off as the PDF is saved.
Regarding the missing pages problem in PDF, could you please make a screenshot that shows your issue in detail and attach it here? I will investigate the issue further and provide you more information.
Best Regards,
Hi Awais,
Yes, I made sure each thread ran one Document object, that is why I was surprised with the run time for the parallel processes. It is almost as if they are not running in parallel. Any other considerations aside from one Document object per thread?
Please check attached screendumps for the missing pages. You can easily confirm this by looking at the last page generated by Aspose:
msword.png = there should be 232 pages here;
picture shows the last 2 pages
pdf-aspose.png = there are only 222 pages; it appears the conversion cut the content of the original ms word file.
Thanks,
Brian
Hi Brian,
Thanks for your inquiry and sorry for the delayed response. We are checking with this scenario and will get back to you as soon as possible.
Best Regards,
Hi Brian,
Thanks for your patience.
Brian:
Yes, I made sure each thread ran one Document object, that is why I was surprised with the run time for the parallel processes. It is almost as if they are not running in parallel.
Could you please share your code here to be able to reproduce this problem on my side? I will investigate it further and provide you more information.
Regarding the missing pages problem, you’re facing during rendering your DOC file to PDF format, I managed to reproduce this issue on my side. I have logged this issue in our bug tracking system. The issue ID is WORDSNET-6635. Your request has also been linked to this issue and you will be notified as soon as it is resolved. Sorry for the inconvenience.
Best Regards,