We do have a solution which is using Aspose.Total for Java to convert doc files into pdf’s. While in most of the cases everything works fine there are situations when problems appear. This happens mainly when original document contains pictures/charts. An end effect can be found in attachment (doc *converted_with_ aspose). Saving doc to pdf directly from Word works fine (doc converted_by_Word) but of course this is not a solution for us - we do have automatic documents processing in place and utilizing Word there would be an overkill. This is why we decided to utilize Aspose.
I’m attaching original document in doc format as well
Thanks for your inquiry. While using the latest version of Aspose.Words i.e. 13.3.0, I managed to reproduce this issue on my side. I have logged this issue in our bug tracking system. The issue ID is WORDSNET-8168. Your request has also been linked to this issue and you will be notified as soon as it is resolved. Sorry for the inconvenience.
The problem is very critical for us to be resolved. You said the issue was created in your tracking system. Would you be able to provide estimate by when I could expect the fix? Unfortunately I cannot tell to the business that “you will be notified as soon as it is resolved”. We can leave for two or three weeks with that issue having a workaround in place (monitoring all conversions, catching those which do have problems with pictures and to convert them manually using Word) but, as you can imagine this is related to high effort and it is error prone anyway.
Unfortunately, your issue is not resolved yet. Our development team has completed the analysis of this issue and the root cause has been determined. The fix to this problem actually requires us to implement a new feature in Aspose.Words’ API and I regret to share with you that the implementation of this new feature has been postponed till a later date. There’s no ETA available at the moment. We will be sure to inform you as soon as this issue is resolved. We apologize for your inconvenience.
The problem occurs because there is an inline image with the diagram in a paragraph having space after 10pt and a tight-wrapped text box below it. Aspose.Words detects that the text box overlaps space after the paragraph and wraps the inline image around the text box. In the meantime while you’re waiting for a fix, you may remove space after the paragraph or reposition the text box slightly downward as a workaround. Please see the following code snippet and attached simplified document:
Document doc = new Document(@“C:\Temp\Simplified.docx”);
Shape s = doc.GetChildNodes(NodeType.Shape,
true)[0] asShape;
the
code included in previous post , in most cases, will fix the issue, but also will
break formatting in shapes which are converting without a bug. Is there a
possibility to find, which shape will be incorrectlyconverted ? When I was converting word to
pdfand with IWarningHandler attached, I
saw a message : "Tight wrapping of a floating shape is not supported.
Square wrapping will be used instead. Wrapped content could be rendered
differently.
At Shape Id:1044 'Text Box 2', Paragraph
47, Section 1
" but I
don't know how to extract shape (node) id and compare with id from above
message
Thanks for your inquiry. I am afraid, the Shape class does not publicly expose the Id property; however, I have logged a new feature request in our issue tracking system as WORDSNET-8225 to be able to get a reference (in Warning method) to the source Node for which the warning is being generated. We will inform you as soon as your issues are resolved. We apologize for any inconvenience.
I have found another bug while converting between word document to pdf document (example in attachments). Y axis label is in wrong position. Could You analyse this example and check if there is an workaround on this issue ?
While using the latest version of Aspose.Words i.e. 13.4.0, I managed to reproduce this issue on my side. I have logged this issue in our bug tracking system and the issue ID is WORDSNET-8250. Your request has also been linked to this issue and you will be notified as soon as it is resolved. Sorry for the inconvenience.
Thanks for your inquiry. Please find below the progress of your issues:
WORDSNET-8168: Our development team has completed the analysis of this issue and the root cause has been identified. However, the implementation of the fix to this issue has been postponed till a later date. We will inform you as soon as this issue is resolved.
WORDSNET-8225: The implementation of this feature has also been postponed till a later date.
WORDSNET-8250: We have a good news for you that is WORDSNET-8250 has now been resolved and its fix will be included in the next release of Aspose.Words (13.5.0) which is planned to be released by the end of May 2013. We will inform you via this forum thread as soon as the new release of Aspose.Words is published.
issues. The former one was analysed and the root cause was identified but in May, when I was asking for the last time, I was told that implementation was postponed till a later date.
The same was done in terms of the latter issue (actually the feature), which means postponing.
Is there any information available if those tasks are going to be implemented in the next release?
I agree on the fact that they should better inform us about the progress of the issues. This topic already is open since the end of April. In my opinion bugs should be fixed faster, but more inportant is that they inform their customers about the progress.
Thanks for your inquiry. Unfortunately, these issues are not resolved yet. I have verified the status of your issues from our issue tracking system and regret to share with you that these issues have been postponed. However, the fix to these problems may definitely come onto the product roadmap in the future. We apologize for your inconvenience.
We understand that these issues are important to you and it is unfortunate that the issues have not yet been fixed. Although we try our best to deal with every customer request in a timely fashion, we unfortunately cannot guarantee a delivery date to every customer issue. Our developers work on issues on a first come, first served basis. We feel this is the fairest and most appropriate way to satisfy the needs of the majority of our customers.
That being said, we fully understand that you are keen to get a fix to your particular issues, please have a look at this page - http://www.aspose.com/corporate/services/priority-support-policies.aspx - purchasing Priority Support will allow you to post your issues in our Priority Support forum and raise the priority of these issues directly with our development teams, if possible, we will then aim to get a resolution to your issue as soon as we can. Many Priority Support customers find that this leads to their issue being fixed in the next release of the software.
I agree with you on the fact that Priority Support is the solution for feature requests. Topics on this forum on the other side very often are about bugs in the Aspose software.
A bugfix request to fix poorly tested software in my opinion almost always time has priority above feature requests. In other words, else Aspose should has tested its software better.
In my scenario it is even different, I’m a Saaspose customer. We are paying a fairly high monthly fee for software full of bugs, resulting in 8% of our conversions that literally crash. Result: we miss an order
Thanks for your input, we do take quality seriously.
We usually release a new product version that contains new features, enhancements and bug fixes. We also try to wrap up a bit more new features into the release. That's the way it works well for us and seems to satisfy the customers.
Before a new version of a software product is released, the common core test cases are run against the new version to make sure that all the old capabilities still work but still It is possible to have a regression issue because of the improvements or while adding a complex feature support. However, we have a separate queue for the issue which appeared in this category. Our development team tries its best to avoid such issues.
Please let me know in case of further assistance or questions.
Hi Imran, thanks for the clear reply. Good to hear that there is a separate list of the current bugs. Should it be an idea to make this list publicly accessible, so everybody can see the current bugfixing progress?
Thanks for your inquiry. According to the above statement, it does not mean that all your reported issues fall in this category. Furthermore, you can ask about the progress of your reported issue(s) in the appropriate forum thread or against the issue id(s). Once the particular issue is resolved, the updates regarding its resolution are shared in the same forum thread where it was reported.