HTML to PDF C# using Aspose.PDF for .NET | Unsupported font style

Aspose.PDF Product Family
21

Hi ShiJien,


Thanks for your inquiry. We have a good news for you, your above reported issue has been resolved and its fix will be included in upcoming release i.e. Aspose.Pdf for .NET 9.8.0. Hopefully this version will be released in first week of November, 2014. However, we will notify you as soon as it is released and gets available for download..

Please feel free to contact us for any further assistance.

Best Regards,f
22

Hi,


It’s going towards the end of 2nd week of November now. I still don’t see any updates nor notification regarding this fix release. Our development team has been waiting for the fix for this issue since early May already. Again, please advice on this, and when can I have the fix ready? Thanks.
23

Hi ShiJien,


Thanks for your patience.

I am afraid we encountered some technical difficulties during build preparation and therefore the release is delayed. However we are working on fixing those issues and we will try our level best to get the new version published, as quickly as possible.
24

Hi,


So, when can I expect it to be out? We have been waiting for so long for this, and I need to mention again that it’s really been impacting our production routine, and we need the fix. It’s either we are provided with temporary workaround or the permanent fix. Thanks.
25

Hi ShiJien,


Thanks for your feedback. As informed above, we are facing some issues in building our new release. Hopefully these will be resolved soon and we will publish it in coming week.

Moreover, your issue has been resolved and its fix will be included in Aspose.Pdf for .NET 9.8.0.

Thanks for your patience and cooperation.

Best Regards,
26

Dear Team/ @tilal.ahmad,
I’m having a legacy code that is using version 9.8.0. I’m also getting a similar kind of error while Creating PDF from HTML document.

Below is the error

Exception Message: The embedded font ‘microsoft jhenghei’ is not found. Make sure that you set correct path to the font file
Source: Aspose.Pdf
StackTrace: at \u008f\u0003\u0013.\u0080\u0005\u000e.\u0016\u009d\u0092(String , Boolean , String , Exception )\r\n at \u008f\u0003\u0013.\u0080\u0005\u000e.FindFont(\u009a\u0005\u000e , String , String , Boolean , Boolean , Boolean , String , Boolean )\r\n at \u008f\u0003\u0013.\u009a\u0005\u000e.\u0093\u001e\u0015(String , String , Boolean , Boolean , Boolean , String , Boolean )\r\n at \u008f\u0003\u0013.\u009a\u0005\u000e.\u0083\u009d\u0092(TextInfo )\r\n at \u008e\u0003\u0013.\u0001\u0004\u000e.\u0002\u009d\u0092(Text , Pdf )\r\n at \u008e\u0003\u0013.\u0001\u0004\u000e.\u0087\u0096\u000f(Pdf , Section , Table , Row , Cell , Text , \u001b\u0003\u000e , \u0005\u0004\u000e , Boolean )\r\n at \u008e\u0003\u0013.\u001e\u0004\u000e.\u0017\u009a(Pdf , Section , HeaderFooter , Table , Row , Cell , Text , \u001b\u0003\u000e , \u0005\u0004\u000e , Boolean )\r\n at \u008e\u0003\u0013.\u0011\u0004\u000e.\u0096\u0097\u000f(Pdf , Section , \u001b\u0003\u000e )\r\n at \u008e\u0003\u0013.\u0089\u0003\u000e.\u0015\u0095\u000f(Pdf )\r\n at \u008e\u0003\u0013.\u0092\u0003\u000e.\u0097\u0095\u000f(\u0015\u0006\u000e , Pdf )\r\n at Aspose.Pdf.Generator.Pdf.Save(Stream stream)\r\n at Aspose.Pdf.Document.\u0010\u0098\u001a(Pdf )\r\n at Aspose.Pdf.Document…ctor(Pdf pdf)

Inner Exception Message: Font ‘microsoft jhenghei’ not found. Please make sure the customer font file is correctly set.

Could you please help me out if this is already fixed in any higher version?

27

@Rahulk17

The linked issue was resolved in 9.8 version of the API. However, it seems like your issue is related to the specific font being not present in the system. Please try to install “Microsoft Jhenghei” font in your system and see if it resolves the issue.

Please also note that we provide support on the basis of latest version of the API which is Aspose.PDF for .NET 21.2. Would you please try to test the scenario with 21.2v of the API and let us know if issue still persists by sharing your sample HTML file in .zip format with us. We will test the scenario in our environment and address it accordingly.