Restrictions and recommendations

Aspose.Words Product Family
1

For now we are developing front system that allows user to print html himself that will pass to aspose generation without modification and now i’m looking some called recommendations which practices and moments we should avoid to proper generation

I found couple by myself, but i’m sure there is possibly more than that?

2

@bloodboilAaromatic

Could you please specify the specific practices or moments you have already identified that should be avoided for proper generation with Aspose.Words?

3

  1. Avoid deeply nested or malformed html structures

  2. Avoid complex css (flexbox, transform)

  3. Explicit content
    Example " Text" or "Text " that causes on your version 24.x (not latest i know) some problems related to overall generations

  4. Avoid comments

  5. Consecutive Formatting tags
    Example: <b><b>Text</b></b>

  6. Better to avoid using <div> <table> or <img> for an Aspose.Cells

We are started to trace aspects like that and preparing special documentation on your side, so i will accept any recommendations or any connected to this thread links to a proper research

4

@bloodboilAaromatic I am afraid, there is no list of restrictions and recommendations to HTML content. In most cases Aspose.Words mimics MS Word behavior when work with HTML content.
Usually Aspose.Words exports roundtrip information to HTML. So if you would like to check how some MS Word feature is expected by Aspose.Words to be represented in HTML, you can simply convert DOCX document to HTML and see how Aspose.Words writes it.