346786 - font.name-list support is 'flaky' (for pages encoded in UTF-8/16) (lang attribute ignores font.name-list)

Status: RESOLVED FIXED

(Core :: Graphics, defect)

Description

[Jungshik Shin]

I have the following font pref. entries:

font.default.ko : sans-serif
font.name.sans-serif.ko : Arial
font.name-list.sans-serif.ko: Gulim, 굴림 
font.name.sans-serif.x-unicode: Arial
font.name-list.sans-serif.x-unicode: Gulim, 굴림 

With the default system locale set to Korean, the lines with no lang specified and with 'lang=ko' specified should be rendered with Arial (ASCII portion) and Gulim(굴림)(Korean and Chinese characters). However, 'CODE2000' is picked up instead for non-ASCII characters. 

If I change font.name.sans-serif.ko to '굴림' (Gulim), 'lang=ko' line is rendered with Arial and Gulim(굴림). 

This problem also affects the font selection in the UI because chromes are all in 'Unicode'. With 'font.name.sans-serif.ko' set to Arial (with Gulim listed in font.name-list.sans-serif.ko), CODE2000 is used throughout the UI (an easy way to see it with en-US version is to bookmark a Korean page with a Korean title 
(and move it to the bookmark toolbar).

Comment 1

[Jungshik Shin]

oops. I meant to give it to pavlov.

Comment 2

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

currently, we don't use font.name-list for lang attribute. But the patch of bug 343454 makes to use it. I think that this bug is fixed by bug 343454.

taking.

Comment 3

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

This may be fixed by bug 343454.

-> FIXED

Comment 4

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

-> REOPEN

We need more work on bug 343454.

Comment 5

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

-> FIXED by bug 343454.