Aspose Word to HTML Conversion – Content Control Inner Content Not Wrapped in <div>

Aspose.Words Product Family
1

Hi,
When I convert a Word document to HTML (either online using the link below or programmatically), I encounter an issue: the inner content of content controls is not wrapped with a <div> tag in the HTML structure. Why is this happening, and how can I resolve it? I am using the latest version of Aspose.

Issue :

1906×577 110 KB

Word Document :
d1a1c3a68566cbfa.docx (32.5 KB)

Output :
d1a1c3a68566cbfa.zip (2.8 KB)

2

@AlpeshChaudhariDev

When converting a Word document to HTML using Aspose.Words, you may notice that the inner content of content controls is not wrapped in <div> tags. This behavior is due to the way Aspose handles content controls during the conversion process. Unfortunately, there is no built-in setting in Aspose.Words that enforces the wrapping of content control inner content in <div> tags.

To address this issue, you can consider the following workarounds:

  1. Post-Processing the HTML: After converting the document to HTML, you can programmatically parse the resulting HTML and wrap the inner content of content controls with <div> tags. This can be accomplished using an HTML parser in your programming language of choice.

  2. Modifying the Document Structure: If you have control over the Word document, consider using styles or other elements that may be better supported during the conversion process.

Here’s a simple example of how you might wrap content in <div> tags using a basic string replacement in C# after conversion:

string htmlContent = ConvertWordToHtml("path/to/document.docx");

// Example of wrapping content control inner content
htmlContent = htmlContent.Replace("<contentControl>", "<div><contentControl>");
htmlContent = htmlContent.Replace("</contentControl>", "</contentControl></div>");

// Save or use the modified HTML
File.WriteAllText("path/to/output.html", htmlContent);

This approach ensures that the content is wrapped as needed, although it requires additional processing after the initial conversion.

If you continue to experience issues or require more specific functionality, consider reaching out to Aspose support for further assistance.

3

@AlpeshChaudhariDev
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): WORDSNET-28629

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

4

The issues you have found earlier (filed as WORDSNET-28629) have been fixed in this Aspose.Words for .NET 25.10 update also available on NuGet.