I recently purchased Aspose Word .Net and found what I believe is a bug. I have attached the uploaded Word doc (CEll1.doc), the conversion to .pdf by Word 2010 (CEll1_Word.pdf) and the conversion to .pdf by Aspose (CEll1_Aspose.pdf). I think Aspose is not recognizing the decimal tab and is left justifying in the cell.
I would like this confirmed as a bug and some estimate on when I can expect a fix.
Hi Scott,
Thanks for your query. I have managed to reproduce the same problem at my end. I have logged this issue in our issue tracking system and you will be notified via this forum thread once this issue is resolved.
We apologize for your inconvenience.
Thanks for your response. Can you tell me when I can expect a fix? If not is a refund available to me? I’ll have to look at other solutions.
Hi Scott,
I have verified the status of this issue from our issue tracking system. The status of this issue is pending for analysis. After analysis, we will be in the position to share any ETA with you.
We appreciate your patience.
Tahir,
Can I get an update please?
Thanks,
Scott
Hi Scott,
I
have verified the status of this issue from our issue tracking system. I regret to share with you that this issue is still pending for for analysis. I will update you via this forum thread once there is any update available on this issue.
We apologize for your inconvenience.
Tahir,
Can I get an update please? I noticed 11.4 is available.
Thanks,
Scott
Hi Scott,
I have verified the status of this issue from our issue tracking system. I regret to share with you that this issue is still pending for for analysis. However, I have requested our development team to provide the expected schedule for the issue. As soon as the issue will be scheduled, I will be more than happy to share the information with you.
I apologize for your inconvenience.
Tahir,
It’s been over a week. I need an update. Your lack of support and communication is not satisfactory. Who can I escalate to?
Scott
Hi Scott,
Thanks for your patience. We understand that this issue is important to you and it is unfortunate that the issue has not yet been fixed yet. We apologise for the inconvenience.
Normally when an issue is reported by a customer it is added to the pool of current issues being worked on by our developers is analysed in a timely manner. However due to the nature of some bugs and the number of features we are working on, this doesn’t always mean we can fix every bug within a short time after it’s reported.
In your case I have asked the development team to analyse this issue and if possible implement it as soon as possible. I will keep you informed of any developments.
Also, would you be happy with a work around for the time being? For example if something other than tabs is used to avoid the current issue but to keep the document looking the same. Would you be happy with that?
I apologise once again for the wait.
Thanks,
Hi Scott,
It has been confirmed the issue you reported is scheduled to be fixed by next month’s release. We will keep you informed of any developments.
Thanks,
Our testing with July’s release shows that this bug was not fixed as you indicated. Please retest with the file I originally attached to this thread and confirm that it is still not fixed.
We have no work around as we have thousdands of documents that would require modification.
Hi Scott,
Thanks for your inquiry.
It is true the developer was unable to finish the fix for this issue before this month’s release. Therefore I have asked him to provide a new fix date and will clarify with him further to make sure things stay on schedule.
I apologise for any inconvenience.
Thanks,
The issues you have found earlier (filed as WORDSNET-6420) have been fixed in this .NET update and this Java update.
This message was posted using Notification2Forum from Downloads module by aspose.notifier.