Issues with the content control during the DOCX to HTML

Aspose.Words Product Family
1

Hello,

I have some issues with the content control during the DOCX to HTML transformation.

First, please find in attachment the files that I used to reproduce the issues.

input.docx : DOCX to convert in HTML

output_aspose.html : HTML converted with Aspose.Word 15.11.0

output_word.html : HTML converted with Microsoft Word

Issue 1 :

When a content control is in another one, the Aspose conversion does not keep the imbrication. The best solution, is to use div blocks to mark the content control, IMO. (see issue_1.png)

Issue 2 :

Sometimes the text into a content control is splitted and each span block are tagged as a content control instead of the p block. (see issue_2.png)

Issue 3 :

When there are more than one paragraph in one content control, the p blocks are splitted and tagged as different content controls. (see issue_3.png)

If you have a look on the HTML converted with Microsoft Word, the result is like those I proposed in the “TO BE” of each screenshot.

2

Hi Raphaël,

Thanks for your inquiry. We have logged these features request in our issue tracking system. Our product team will look into the possibility of implementation of these features. Once we have any information about these features, we will update you via this forum thread. Please let us know if you have any more queries.

*crobin_airbus:
Issue 1 :
When a content control is in another one, the Aspose conversion does not keep the imbrication. The best solution, is to use div blocks to mark the content control, IMO. (see issue_1.png)

Issue 3 :
When there are more than one paragraph in one content control, the p blocks are splitted and tagged as different content controls. (see issue_3.png)*

The issue ID is WORDSNET-12833.

crobin_airbus:
Issue 2 :
Sometimes the text into a content control is splitted and each span block are tagged as a content control instead of the p block. (see issue_2.png)

The issue ID is WORDSNET-12834.

3

Dear Support team,

Thanks for this feedback.
Is it possible to have a planning for the relosution of these bugs?

Many thanks in advance.

Raphaël

4

Hi Raphaël,

Regarding WORDSNET-12833 and WORDSNET-12834, our product team has planned to integrate the fixes to these issues in Aspose.Words’ 16.2.0 - Feb 2016 release. If everything goes by plan, we are very hopeful to include the fixes to these issues in Aspose.Words’ February 2016 release but please note that this estimate is not final at the moment. We will inform you via this thread as soon as your issues are resolved. We apologize for any inconvenience.

Best regards,

5

Dear Support team, Thanks for this feedback. Is it possible to have a planning for the relosution of these bugs? Many thanks in advance. Raphaël

6

Hi Raphaël,

Thanks for your inquiry. Hopefully, the fix of these issues will be available in February 2016 release. Please note that this estimate is not final at the moment. We will be sure to inform you via this forum thread as soon as these issues are resolved.

We appreciate your patience.

7

Thanks a lot.

8

Hello,
it seems that WORDSNET-12833 and WORDSNET-12834 are not in the lats delivery of Aspose.Words for .NET 16.2.
It is disapointing for my users.
Could you give me some information on that ?
Best regards
Daniel Stephan
Application Services Manager
Airbus

9

Hi Daniel,

Thanks for your inquiry. We have verified the status of WORDSNET-12833 and WORDSNET-12834 from our issue tracking system and regret to share with you that both issues are not resolved yet.

We have asked from our product team about the ETA of these issues. As soon as any information is shared by them, we will be more than happy to share that with you.

We apologize for your inconvenience.

10

Hi Daniel,

The issue WORDSNET-12833 has been resolved and its fix will be available in next version of Aspose.Words v16.4.0.

Now, we enclose all STD nodes with div tags as shown in following html snippet:

This text should be enclosed in SDT4 div
This text should be enclosed in SDT4 div

Please let us know if this fulfill your requirements. We will close WORDSNET-12834 (Export SDT style properties into P tag instead of Span tag).

11

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

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