We have logged these details in our issue tracking system and will keep you posted on any further updates.
Regarding WORDSNET-18368, we have completed the work on this issue and come to a conclusion to close this issue as “Won’t fix”.
The difference between Aspose.Words and MS Word outputs is rather minor and we consider it acceptable. We converted the original document to PDF by using MS Word 2016, and the result, although slightly, differs from what you provided. Some areas of image are better than MS Word output, some worse. Apparently, the result may vary somewhat from system to system and in different versions of MS Word. The perfect match will not be achieved, because we do not know the exact internal logic of MS Word. For the current result, the difference is insignificant.
Fine we will try for version updates.Can you resolve the other PDF conversion issues stated above?
Please check below the status of your outstanding issues:
- We have completed the analysis of the following issues and identified the root causes of the problems. However, because of complexity, the implementations of these issues have been postponed till a later date (no estimates are available at the moment).
WORDSNET-18290, WORDSNET-18331, WORDSNET-18333, WORDSNET-18334 and WORDSNET-18370
The fix of WORDSNET-18332 is being developed.
WORDSJAVA-2006 is currently pending for analysis and is in the queue.
We will inform you via this thread as soon as these issues are resolved. We apologize for any inconvenience.
Yeah, will check the same.
Regarding WORDSJAVA-2006, please use the following workaround to fix this issue:
Document doc = new Document("E:\\temp\\10N760L2HNR_10_egi10N760L2HNR.doc"); PdfSaveOptions options = new PdfSaveOptions(); options.getMetafileRenderingOptions().setRenderingMode(MetafileRenderingMode.VECTOR); doc.save("E:\\temp\\awjava-19.5-opts.pdf", options);
A post was merged into an existing topic: Preserve Document Elements during Word to PDF Conversion