Need More Info
Last Updated: 19 Oct 2020 18:19 by ADMIN
Katsuyiki
Created on: 13 Oct 2020 00:46
Type: Bug Report
0
Kanji is not displayed in the print preview

We use telerik reporting service in ASP.NET Core 3 on CentOS 8 server.
I just confused in spesific kanji is not show in preview and pdf.

"備考" is not shown,but "考備" is shown, reason why?(see attached xslx file)
Private Font settings will be fine(see attached reportsettings.json),because of gothic and mincho font is displayed.
If set double byte space ("備考 ") is displyaed... I dont know reason why.

We install libgdiplus API in cent OS server, but not well.
hiragana is OK, but some types of Kanji is Not OK.

We already running on Windows server is not having same issue(always displayed)

We think some issue in textbox sizing algorythm in Telerik Reporing on Linux ( I used latest version 14.2.20.916)

We look forward to hearing from you.

1 comment
ADMIN
Ivan Hristov
Posted on: 19 Oct 2020 18:19

Hi Katsuyiki,

I'm sorry to hear you're experiencing troubles with our product and its kanji rendering on Linux. As you've noticed, the rendering experience on Linux differs from the one on Windows because the libgdiplus library, which is used as a substitute for Windows' GDI+, has some rendering issues. As we discovered when investigating scenarios from our users that experience similar problems, usually the problem is related with fonts that do not support the whole Unicode table for Chinese or Japanese characters.

I noticed that in the attached report you're using IPA fonts, but can you please try substituting them with a font like Microsoft JhengHei, which is known to work in similar cases. You can also check other fonts from this list that contains fonts that cover all or the most of the Chinese characters - you can try some of them and see if the issue will be resolved.

You can also see if the IPA font set in the report has been substituted by another font during report rendering. This may happen because the IPA font cannot be loaded by the engine and in this case the font is automatically substituted by another font, which may not support all the characters. This information is output in the trace file and you can enable the trace logging by following the steps described here: Troubleshooting reporting implementation into ASP.NET Core application.

Hope this helps.

Regards,
Ivan Hristov
Progress Telerik