Incorrect font and radio button missing value when export html to doc

Aspose.Words Product Family
1

Hi there,

I’m using word-13.1-jdk16.jar to export my html to doc. But I have faced some problem when exporting my html:

1. All the fonts in my html are incorrect after export. It should be Arial but appears to be Time News Roman.
2. All selected radio button can not be display in exported doc:



3. My stylesheet doesn’t apply well in exported document.

Have anyone faced this before ? Please help me or guide me to the right topic.

Thanks in advanced.
Tam Nguyen Minh

2
Hi Tam,

Thanks for your inquiry. Could you please attach your input Html file and output Word document showing the undesired behaviour here for testing? I will investigate the issue on my side and provide you more information.

Best regards,
3

Hi Awais,

Thank you for answering me. Please find my exported doc and html files as attachment.
I already try 2 ways below to generate doc or pdf file, but get the same result

1.
String html = //generate html code;
Document document = new Document();
com.aspose.words.DocumentBuilder builder = new com.aspose.words.DocumentBuilder(document);
builder.insertHtml(html);
document.save(“D:\newoutput.doc”);

2.
InputStream content = // get html
LoadOptions option = new LoadOptions();
option.setLoadFormat(LoadFormat.HTML);
com.aspose.words.Document input = new com.aspose.words.Document(content, option);
DocSaveOptions options = new DocSaveOptions();
options.setSaveFormat(SaveFormat.DOC);
os = new FileBackedOutputStream(THRESHOLD);
input.save(os, options);

Please point me out if there are any incorrect in my html or my java code.

Thanks in advanced
Tam Nguyen Minh

4

Hi Tam,


Thanks for your inquiry. While using the latest version of Aspose.Words i.e. 13.7.0, I managed to reproduce these issues on my side. I have logged the following two issues in our bug tracking system.

WORDSNET-8825: Incorrect font is applied to Paragraphs when importing

tags from Html

WORDSNET-8826: Import radio input html field as HTMLCONTROL Forms.HTML:Option.1

Your request has also been linked to these issues and you will be notified as soon as they are resolved. Sorry for the inconvenience.

Moreover, please visit the following link to learn about what style features are supported on HTML import:

Best regards,

5

Thank you, Awais

I will wait for bug fixing notification. Mean while, I will try to refactor my css with your link.

6

Hi Awais,

I must get back to this problem since we are going to meet the deadline soon. Can I get some update about these current issue ? Do we need to purchase a new license for latest release (include these bug fix) or these issues will be included in some patch of my current version word 13.1-jdk16

Thank you and Best regards
Tam Nguyen Minh

7

Hi Tam,


Thanks for your inquiry. Unfortunately, your issues are not resolved yet. I have verified the status of these issues from our issue tracking system and regret to share with you that these issues have been postponed till a later date. We will be sure to inform you via this thread of any developments and let you know once they are resolved. We apologize for your inconvenience.

Secondly, the license files come with an expiry date which determines whether you can free upgrade to a version of Aspose.Words that is published before or on that expiry date. Therefore, you always need to have a valid subscription to be able to use the latest released version of Aspose.Words.

Best regards,
8

The issues you have found earlier (filed as WORDSNET-8825) have been fixed in this .NET update and this Java update.

This message was posted using Notification2Forum from Downloads module by aspose.notifier.
9

Hi, is there a plan to fix WORDSNET-8826? It has been over a year now.


Thanks
10
Hi Tam,

Thanks for your inquiry. Unfortunately, your issue is not resolved yet. At the moment, there is no way to create ActiveX controls using Aspose.Words document model. So, this problem actually requires us to implement a new feature in Aspose.Words and we regret to share with you that implementation of this issue has been postponed. However, the fix of this problem may definitely come onto the product roadmap in the future. Unfortunately, we can not promise a resolution any time soon. We apologize for your inconvenience.

Best regards,
11

The issues you have found earlier (filed as WORDSNET-8826) have been fixed in this .NET update and this Java update.

This message was posted using Notification2Forum from Downloads module by aspose.notifier.