we are encountering the following issue which we are using Product Name (Aspose.pdf), version (17.7), C# language running console program at Windows Server.
Admin User reported image files which Chinese characters are being rendered incorrectly in resultant image (some Chinese wordings Not fine), please advice how to solve, thanks
Please try using the latest version of the API i.e. 24.7 and make sure that all Windows Fonts (specifically that support Chinese) are installed correctly in the Windows Server environment. In case issue still persists, please share your sample file and the code snippet with us. We will test the scenario in our environment and address it accordingly.
img1.png (90.9 KB)
Our server has installed Chinese font and I tried update dll to version 22.5, but the issue is still existed.
img2.png (10.2 KB)
Please share your sample PDF with us so that we can test the scenario in our environment and address it accordingly.
We had not physical PDF file because the pdf is generated from program in memory like the following
Aspose.Pdf.Document UWDoc = new Aspose.Pdf.Document((new MemoryStream(Encoding.UTF8.GetBytes(UnderwritingHTML))), htmloptions);
in img1, the following wording something wrong
其他, 請說明
a) 已進行的治療 / 檢查 / 測試 / 掃描
Aspose.Pdf.Document UWDoc = new Aspose.Pdf.Document((new MemoryStream(Encoding.UTF8.GetBytes(UnderwritingHTML))), htmloptions);
UWDoc.Save(“gc.pdf”); //for debug
fig2.png (65.7 KB)
the issue is this code which cannot covert all characters correctly
Aspose.Pdf.Document UWDoc = new Aspose.Pdf.Document((new MemoryStream(Encoding.UTF8.GetBytes(UnderwritingHTML))), htmloptions);
you can test the aspose product with the following code which will show the production issue easily
Aspose.Pdf.Document UWDoc = new Aspose.Pdf.Document();
Aspose.Pdf.Page page = UWDoc.Pages.Add();
page.Paragraphs.Add(new Aspose.Pdf.Text.TextFragment("請說明"));
page.Paragraphs.Add(new Aspose.Pdf.Text.TextFragment("a) 已進行的治療 / 檢查 / 測試 / 掃描 及 b) 有關治療 / 檢查 / 測試 / 掃描日期"));
UWDoc.Save("gc15.pdf");
any update at production issue of mentioned sample code?
ok, thanks in advence
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): PDFNET-57753
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
passed 4 days already, any update at ASPOSE.PDF product issue?
The ticket has recently been logged and will be prioritized on a first come first serve basis as per free support policies. Its resolution time depends upon its complexity as well as the number of issues in the queue logged prior to it. We will inform you once we make any progress towards its resolution. Please spare us some time.
We are sorry for the inconvenience.
could you estimate the completion date of fixing issue of not supporting Chinese Font at ASPOSE.PDF? We need to reply our end-user the date of fixing date with third-party vendor, thanks.
fig4.png (53.4 KB)
for your information, line 1470 cannot work to set htmloptions to correct chinese font, so that the issue is occurred at the PDF.Document which (UWDoc) store issued chinese wording inside
We are afraid that we cannot share any ETA at the moment as the ticket has not been investigated yet. As shared earlier, we will investigate the issue on first come first serve basis as per free support policies. Your concerns have been recorded as well and we will surely let you know as soon as we have some information about ETA or ticket investigation.
The information you just provided, has also been logged under the ticket and we will investigate from this perspective as well. We do recommend you check out priority support option in case the issue is a show stopper for you. In the meanwhile, we will keep you informed about the issue progress. We apologize for the inconvenience.
you can cancel the ticket, I fixed it already, thanks
Thanks for the feedback and it is nice to hear that you have been able to sort out your issue. Please allow us to perform some investigation so that we can post a solution here as well for others who might have similar issue.