Hi Stanislav,
Thank you for reporting this problem to us. I managed to reproduce the problem on my side. Your request has been linked to the appropriate issue. The problem is planned to be fixed in the next version of Aspose.Words. You will be notified as soon as it is resolved.
Best regards,
Again, thank you very much for your help.
Stanislav.
Hi Alexey,
I talked to my bosses again and they asked again to see if there is an option to make phone conversation with yours product manager (or somebody else that in charge of product) to see when we can get answers to all problems (it not suppose to be technical conversation). It is problematic to wait till end of May because we must make decision now. The conversation will be done by my bosses and not by me.
Thanks,
Stanislav.
Hi Stanislav,
Thank you for considering to use Aspose.Words in your solution. Using Aspose.Words to replace MS Word automation is one of the core concepts of the Aspose.Words strategy. We definitely want our customers to succeed with using Aspose.Words for this purpose.
One of the most important reasons Aspose.Words can be used to replace MS Word automation is the fidelity of conversions and rendering that Aspose.Words provides. E.g. Aspose.Words tries to convert documents in exactly the same way as MS Word would have done that.
But one inherent issue that is always around in this area is that it is difficult to guarantee 100% same behavior on all documents you can encounter. The Word document formats are complex and both the formats and the rendering behavior of MS Word is full of quirks that they have accummulated over the 25 years of MS Word history.
At Aspose.Words we have already achieved the fidelity far beyond of any competitors and we spend a lot of effort to improve this even further, there is always a possibility that some documents will not convert exactly like MS Word does. We will endeavor to resolve such issues, but we do not guarantee particular timeframes.
Before you proceed with Aspose.Words I would recommend you try it on as many documents you and your customers will need to process as possible. Then you can have a better picture of how many fidelity differences you have and how serious they are to you and to your customers.
If you and your customers absolutely cannot live with any formatting loss, then it is probably in your best interests not to proceed with Aspose.Words right now. You might be able to come back in several months time, for example when you have next major release of your solution to see if Aspose.Words fidelity level has increased enough to satisfy your needs.
----------
As for the issues you reported:
WORDSNET-26683 - Labels of list show incorrect when open generated rtf document in WordPad
This has not been analyzed yet, but it will be done today.
WORDSNET-24062 - Images are invisible in WordPad when open RTF produced by AW.
This has been analyzed as follows:
When MS Word saves an image to RTF format it produces two control words shppict and nonshppict (for backward compatiblity). AW does the same but the difference is that MSWord saves picture as WMF (wmetafile8) in nonshppict section while AW emits jpegblip for both sppict and nonshppict.
Since WordPad and some other readers doesn’t understand jpegblip the image gets ignored.
It seems that we need to pack JPEG to WMF in order to be compatible with WordPad, OpenOffice and other readers.
It is scheduled for implementation in 10.1 and release end of May.
-—
But please review my explanation of fidelity problems above. What I am worried about is that you from time to time continue experiencing these issues. And if every such issue will be as critical to you as these two, then it might create a lot of problems for you and four us.
Just to let you know 26683 will also be included in 10.1 end of May. The problem is due to Aspose.Words not writing a completely expanded list label formatting to RTF and the “old readers” like in WordPad rely on it to display list labels properly.
Hi, Roman,
Thank you very much for reply. I forwarded your answer to my bosses.
Thank you,
Stanislav.
The issues you have found earlier (filed as 24062;26683) have been fixed in this .NET update and in this Java update.
This message was posted using Notification2Forum from Downloads module by aspose.notifier.
It is a great news!! Thank you!
I will perform the testing later this week.
Thank you,
Stanislav.