We have a large Microsoft Word document (24MB) that can be found at http://test.infosphere.com.au/files/Aspose/
. Our product saves it as a PDF file using Aspose.Words, but is successfully converting less then half of the images.
If I create a stand alone program that does the conversion of this large file it works.
Thinking this is a memory issue I get our product loaded in the debugger, ready to step into the line of code that does the pdf conversion
Dim oWordDoc as New Aspose.Words.Document(vsDocPathAndName)
oWordDoc.Save(vsPdfPathAndName)
So the memory hit on my machine is similar (or higher) to the conditions where we are seeing failure of all images to convert.
Now I switch to my stand alone program and run that thinking perhaps I will get a similar result with not all images being converted.
This was not the case. Again the stand alone utility was 100% successful.
The inputs in both cases are identical, this large file. Yet the outputs differ.
As I understand the first line of code above
Dim oWordDoc as New Aspose.Words.Document(vsDocPathAndName)
creates the DOM structure of the document. It is this process that is possibly not representing all images found in the document into the DOM structure.
The second line of code
oWordDoc.Save(vsPdfPathAndName)
Builds the PDF file based on what is in its DOM structure. It is this process that is possibly not creating all the images it has in the DOM structure into the PDF document.
Under what conditions will Aspose.Words
- not create all images found in a source Word document into the DOM structure
- not create all images found in the DOM structure into the PDF document.
Any other ideas?
We are using the latest trial version as downloaded two weeks ago, with an unlimited license.
Thanks
Tim