New issue
Advanced search Search tips

Issue 884841 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Chrome does not render correct text in Korean language in Chrome with font "_sans" in Flash

Project Member Reported by jecl...@adobe.com, Sep 17

Issue description

FAIL : WIN 10 / CHROME / 28.0.0.137 / 23.0.0.208
PASS : WIN 10 / IE / 28.0.0.137 / 23.0.0.208

Method:
1. Open the zip file. 
2. Run korea-issue.html in IE and Chrome.

Result:
Text is not rendered correctly in TLFTextField in Chrome. Korean text is redered perfectly in regular textfield. Text is rendered correct in both regular textfield and TLFTextField in IE.

Expected:
Text should render correctly in Chrome.

----- 

Analysis: 

This issue is about Chrome PPAPI not rendering "Malgun Gothic" and "Malgun Gothic Semilight" font correctly.

There are 2 issues in Chrome:

(1) Chrome resolves "Malgun Gothic" font to "Malgun Gothic Semilight" through PPAPI fontfile interface.

The attached "ko_TLF_Malgun-Gothic-Regular_win10" test can be used to demonstrate this issue.

By default, FontFile PPAPI is available, so the rendering result is not correct. If we disable FontFile PPAPI and force Flash Player to access font through Win GDI, it shows the correct result. This indicates that if font name "Malgun Gothic" is handled properly, Flash Player should render it as expected.

(2) "Malgun Gothic Semilight" is not handled correctly by Chrome

Attached 3 png files shows the text rendering comparison between "Malgun Gothic" font and "Malgun Gothic Semilight" font. Both IE11 and Firefox show the difference between the 2 fonts, but Chrome seems to handle "Malgun Gothic Semilight" in the same way as "Malgun Gothic"

We used a simple string to investigate the issue: "니다", the unicode encoding of the string is {0xB2C8, 0xB2E4}

With "Malgun Gothic" font, the GIDs are resolved as {0x0422, 0x042C}

With "Malgun Gothic Semilight" font, the GIDs are resolved as {0x0BF8, 0x0C14}

 

In Firefox, Flash Player passes the GIDs and the font info to Win32 API, and the text is rendered correctly.

In Chrome, Flash Player passes the same information to PPAPI, the text is not rendered as expected.

 

Summary:

We don't know how Chrome handles "Malgun Gothic Semilight" font, the above observation shows that Chrome is likely to have some problem in this area.

 

Permalink Edit Delete
xzhang Xing Zhang added a comment - 17/Aug/18 15:58
This is related to fontfile PPAPI. It always resolves "_sans", or even "Malgun Gothic" fonts to "Malgun Gothic Semilight", it should resolve to "Malgun Gothic".

If I disable fontfile PPAPI and switch back to PPAPI GDI interface, it works fine.
 
Korean issue.zip
347 KB Download
malgun_font_test_chrome.png
17.4 KB View Download
malgun_font_test_firefox.png
18.0 KB View Download
malgun_font_test_ie11.png
18.2 KB View Download
ko_TLF_Malgun-Gothic-Regular_win10.fla
5.6 KB Download
ko_TLF_Malgun-Gothic-Regular_win10.html
2.2 KB View Download
ko_TLF_Malgun-Gothic-Regular_win10.swf
19.7 KB Download
ko_TLF_Malgun-Gothic-Semilight_win10.fla
5.8 KB Download
ko_TLF_Malgun-Gothic-Semilight_win10.html
2.2 KB View Download
ko_TLF_Malgun-Gothic-Semilight_win10.swf
19.7 KB Download
Components: Internals>Plugins>Flash

Sign in to add a comment