Three level thai language rendering issue when converting html to pdf format


We are using Aspose Word to make pdf document from html document. In our html we have three level thai characters/content, the rendering of thai is disturbed and characters are collapsed.

See original output in this image:

Thai Box 1.png (1.7 KB)

And the collapsed output in pdf:

Thai Box 2.jpg (2.9 KB)

The code we are using is as follows:
string pdfFilePath = @"[DirectoryName]:\Myhtmlfile.html";

Document htmlDoc = new Document(htmlFilePath, new Aspose.Words.HtmlLoadOptions() {LoadFormat =LoadFormat.Html, Encoding = Encoding.UTF8});

SaveOutputParameters param = htmlDoc.Save(pdfFilePath);

We have tried both version 17 and 18.

Input html is attached here:

Smart Report of thai three (1.3 KB)

Any help in this regard is highly appreciated.



We tested the scenario and managed to reproduce the same problem on our end. For the sake of correction, we have logged this problem in our issue tracking system. The ID of this issue is WORDSNET-17817. We will further look into the details of this problem and will keep you updated on the status of correction. We apologize for your inconvenience.

Thanks awais,

Can you please tell us a deadline of availability of this fixing because our clients are waiting for the release. This issue is very critical for us.



This issue is currently pending for analysis and is in the queue. There are no estimates available at the moment. We will inform you via this thread as soon as this issue is resolved. We apologize for any inconvenience.

awais, actually we switched to aspose because of its multi lingual support specially thai and mandarin languages but now we are stuck in this issue. We are about to purchase aspose license in a day or two. We found an interesting finding that this is working fine on two of our machines but not working on rest of the machines. If it is system/environment based issue can you please help us to identify the root cause or changes required to fix this issue on machines so that we can apply them until some other arrangment is made?


Thanks for your inquiry. We try our best to deal with every customer request in a timely fashion, we unfortunately cannot guarantee a delivery date to every customer issue. We work on issues on a first come, first served basis. We feel this is the fairest and most appropriate way to satisfy the needs of the majority of our customers.

Currently, your issue is pending for analysis and is in the queue. Once we complete the analysis of your issue, we will then be able to provide you an estimate.

You reported this issue in free support forum and it will be treated with normal priority. To speed up the progress of issue’s resolution, we suggest you please check our paid support policies from following link.
Paid Support Policies

Ok we will go for the paid support but I am eager to know how much time will it take to fix this issue in paid support, for instance 24-48 hours or so?

Thanks and Regards.


I am afraid, we cannot share exact time frame at the moment as this issue is currently pending for analysis and is in the queue (containing issues with normal priority).

Generally, purchasing ‘Paid Support’ will allow you to post your issues in our Paid Support Helpdesk and raise the priority of this issue. Many ‘Paid Support’ customers find that this leads to their issues being fixed in the next release of the software.

If you would like to take advantage of the ‘Paid Support’ then please request a quote in our purchase forum - Aspose.Purchase - Free Support Forum -

Thanks awais, please tell us what is your frequency of releases i.e. usually after how much time a build is released?



We publish a new version of Aspose.Words at the start of every month.

Also, regarding my previous reply here, the Thai script requires shaping that is not currently supported by Aspose.Words yet. So, raising the support level would not help to resolve the issue faster as we are currently working on adding support for complex scripts such as Thai in Aspose.Words.

We will inform you via this thread as soon as this issue will be resolved in future. We apologize for any inconvenience.

We have purchased paid support. What about the issues posted on free support, should we repost them to paid support?


Yes, please use your paid support account to directly post your important queries in Paid Support Helpdesk .

Also, please mention the existing free support forum thread link of the issue that you want to raise the priority of.

I am currently having the same issue with Apose.Words v22.8.0. Was this ever resolved?

@rmo Unfortunately, the issue WORDSNET-17817 is not yet resolved. It is currently postponed and is not yet scheduled for development.