Hi,
Screenshot attached.
Hi Mariusz,
Thanks for contacting support.
I have tested the scenario with following code snippet while using Aspose.Pdf for Java 17.4 and was unable to notice any issue. The output file was generated correctly and there were no missing Chinese Characters in it.
HtmlLoadOptions htmloptions = **new** HtmlLoadOptions(dataDir);
htmloptions.setInputEncoding("UTF-8");
Document pdf = **new** Document(dataDir + "CN-B-2016-00093.htm", htmloptions);
pdf.save(dataDir + "CN-B-2016-00093_out.pdf");
For your reference, I have also attached an output, generated by above code. We will appreciate if you please share some more information (i.e API Version, OS Version, JDK Version, etc), so that we can test the scenario again in our environment and address it accordingly.
Best Regards,
We’re using Aspose.PDF for Java 17.4, it is running on Tomcat using JDK 1.7, Windows Server 2012. It happens every time.
I tried running the same code on Mac OS/JDK 1.6 and the output PDF is correct. What could be the reason it doesn’t work correctly on Windows? The same issue we observe on our CentOS environment.
Hi Mariusz,
Hi,
We are facing similar issue while converting HTML to PDF in Chinese or Japanese language. On CentOS, the resultant PDF file contains box characters in it.
Can we know the status of the issue PDFJAVA-36805?
Best Regards,
Rakshitha
Thanks for your inquiry.
The earlier logged issue was resolved. Since the logged issue was moved to priority support, resolution update was shared in respective forums. We found that this issue could be fixed by installing the font Arial Unicode MS that has all required characters.
Please, install the font in default font directory or set a path to the font using the Document.addLocalFontPath()
function. Please also make sure to use latest version of Aspose.PDF for Java i.e. 18.6. In case of any further assistance, please feel free to let us know.
Hi Ali,
This worked. Thanks for your inputs.
Best Regards,
Rakshitha
Thanks for your kind feedback.
It is good to know that your issue has been resolved by suggested approach. Please keep using our API and in case of any further assistance or inquiry, please feel free to create a new topic.