Rendering bullits broke from Aspose 13.9 -> 13.10 (#45773)

Aspose.Words Product Family
1

Hi,


We have an issue with the indentation of bullits (
  • ) when they contain

    tags.

    • When the
  • contains a

    it gets another indentation. This is also the case in a browser. To fix the indentation we added some styles to compensate. After these style changes the browser shows the html as we expect.


    • We use insertHtml of the document builder to create the Word document based on the source html. This worked fine when using Aspose 13.5 and Aspose 13.9. (See printtest460 OK resultAspose13.9.doc in the attachment)

    However, starting from version 13.10 and up our html is not converted correctly to word. (See printtest460 NOTOK resultAspose13.10.doc) The indentation differs, and also the fontsize is different when the
  • contained a

    .


    • I included the source html we use (printtest460.html), and I also added the result when we used Aspose 13.9 and the result when we used Aspose 13.10. (I also tested with the 14.11, and this still contains the issue).

    I only included the source html and the results. If you want to, I can send my entire test project, but I don’t think this adds any helpful information. If you want my test project, just ask and I’ll upload it.

    Can you also reproduce this issue? Hopefuly you can fix this in a upcoming release, since I don’t know how to work around this issue.

    Best regards,
    Robert Wielink
    Infoland BV
    2

    Hi Robert,

    Thanks for your inquiry. I have tested the scenario and have managed to reproduce the left indent issue at my side. For the sake of correction, I have logged this problem in our issue tracking system as WORDSNET-11277. I have linked this forum thread to the same issue and you will be notified via this forum thread once this issue is resolved. We apologize for your inconvenience.

    Regarding font size, this is not an issue. When input document is opened in browser, the font size is different for list items. Please let us know if you have any more queries.

    3

    Is there any workaround we can implement until a fix is available?

    4

    Hi Robert,

    Thanks for your inquiry. Unfortunately, there is no workaround available for this issue. We will update you via this forum thread once this issue is resolved.

    We apologize for your inconvenience.

    5

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

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

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

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