Math equations (Symbol font) not correctly converted - problem only in Internet Explorer

Dear Aspose support,

when opening the result HTML of a conversion of an RTF document with Aspose.Word browsers like Chrome or Firefox don’t have any issues, but Internet Explorer 11 (version 11.0.9600.18665) running on Windows 7 does not correctly display the Symbol fonts. you can see the result as screenshot ‘ie11_result.PNG’.

There is also an error in the developer console (see the attached png screenshot ‘ie_console_error.PNG’), that does not appear in the other browsers and could be related to the issue.
As soon as I change the special UTF-8 characters for the greek symbols to latin characters, the result is displayed correctly.

I zipped the input RTF and the resulting HTML and attached them as ‘’.

ie_console_error.PNG (8.5 KB) (90.8 KB)
ie11_result.PNG (30.9 KB)

The Aspose API we are using: Aspose-Words for Java 17.5

Code example (very straight forward):

public void convertToHtml(InputStream inputStream, OutputStream outputStream) {
    try {
        Document doc = new Document(inputStream);, saveOptions);
    } catch (Exception e) {
        LOG.error("Convert to html failed with exception", e.getMessage());
        throw new ConversionException("Convert to html failed", e);


 public SaveOptions createSaveOptions() {
    HtmlFixedSaveOptions options = new HtmlFixedSaveOptions();
         return options;

Kind regards,
Stefan Raubal


Thanks for your inquiry. We have tested the scenario and noticed the reported issue. We have logged a ticket WORDSNET-15574 in our issue tracking system for further investigation and rectification. We will notify you as soon as it is resolved.

We are sorry for the inconvenience.

Best Regards,

Thank you for your investigations and for creating an issue in your issue tracking system.
Looking forward to the fix.

Kind regards,
Stefan Raubal

Dear Aspose support,

is there any progress on this issue?

And is there a way to check the status of items in your issue tracking system?

Kind regards,


We regret to share with you that the implementation of this issue has been postponed (no estimate is available at the moment). We will inform you via this thread as soon as this issue is resolved. We apologize for your inconvenience.