We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Different result converting RTF-File to PDF and HTM

Hi,
I am using aspose.words 17.9 but have following problem:
Converting rtf to pdf and html using this attached rtf-File does not create same result.
I created a standalone demo-application (AsposeBug). The wrong result is in AsposeTest.zip.

AsposeTest.zip (91.5 KB)

Kind regards,
Hendrik

I do not know, why it is not possible to upload the AsposeBug.zip… This Forum does not upload it.

@abbenhaushe,

Thanks for your inquiry. To attach the resources, please zip and upload them.

Please attach the following resources here for testing:

  • Your input RTF document.
  • Please create a simple Java application (source code without compilation errors) that helps us to reproduce your problem on our end and attach it here for testing.

As soon as you get these pieces of information ready, we’ll start investigation into your issue and provide you more information. Thanks for your cooperation.

Thanks for your Support. You will find the rtf-document inside this simple demo application: AsposeBug.zip (515.1 KB)

Please add aspose-words-17.9-jdk16.jar to lib directory.
Kind regards,

Hendrik

@abbenhaushe,

Thanks for sharing the detail. Please note that PDF and HTML formats are quite different so sometimes it’s hard to achieve 100% fidelity. Aspose.Words mimics the behavior of MS Word. If you convert your RTF to PDF or HTML using MS Word, you will get the same results.

In your case, we suggest you please save the RTF to HTML_FIXED file format. Hope this helps you.

Document doc = new Document(MyDir + "input.rtf"); 
doc.save(MyDir + "output.html", SaveFormat.HTML_FIXED);

Thanks for your feedback. The HTML_FIXED file format does technically work but does not work in our case. Currently we have a licence for 15.8.0 until 16.7.0. This old version does not have this issue, but has other issues, why we would like to update to a newer version of aspose. In Version 15.11.0 the issue already exist, so the issue seems to be added between 15.8.0 and 15.11.0. If you would fix this issue, we would renew our licence to Version 17.9.

@abbenhaushe,

Thanks for sharing the detail. Please note that the latest version of Aspose.Words 18.1 mimics the behavior of MS Word. If you compare the output generated by Aspose.Words and MS Word, you will notice that the Aspose.Words’ output is better. However, we have logged this issue as WORDSNET-16373 in our issue tracking system. We will inform you via this forum thread once there is any update available on this issue.

We apologize for your inconvenience.

Thanks for creating the issue WORDSNET-16373. The status of this issue changed to “Postponed”. What does this mean in your development planning? When can we expect to get a fixed version?

Thanks for your support.

@abbenhaushe,

Thanks for your inquiry. We regret to share with you that this issue has been postponed. The underlying problem here is complex and involves many internal tests as well. We will inform you via this forum thread once there are any further developments.

We apologize for your inconvenience.

hey,

are there any further developments or do you know when you will start fixing this issue?
Kind regards,

Hendrik

@abbenhaushe,

Thanks for your inquiry. Unfortunately, there is no update available on this issue. We apologize for your inconvenience.

You reported this issue in free support forum and it will be treated with normal priority. To speed up the progress of issue’s resolution, we suggest you please check our paid support policies from following link.
Paid Support Policies

Thanks for your feedback. If we decide to get your paid Developer Support, do you assure to provide a fix for this issue within 3 months?

King regards,

Hendrik

@abbenhaushe,

Thanks for your inquiry. If you buy paid support, we will schedule this issue for development. Regarding the delivery date of the fix, please check the conditions of paid support from here:
Paid Support Policies

hey,

are there any updates to this issue?

Kind regards,
Hendrik

@abbenhaushe,

Currently, there is no update available on this issue. We will inform you via this thread as soon as it is resolved. We apologize for your inconvenience.