756866 - Korean character styled bold

Status: RESOLVED FIXED

(Firefox for Android Graveyard :: General, defect)

Description

[Channy Yun [:channy]]

Attachment: comparision Korean font with android default browser.

Korean character alway styled bold in Fennec aurora and beta.
This bug is similar with bug 754883. 

In case of chinese and japanese character is shown nomally.
Please check out other locale version.

* Tested phone: Samsung Galuxy SII
* Locale version: en-US, ko

Comment 1

[Channy Yun [:channy]]

According to my investigation, in https://hg.mozilla.org/releases/mozilla-aurora/file/0984ec812496/modules/libpref/src/init/all.js#l2809

- pref("font.name.sans-serif.ko", "Droid Sans");
+ pref("font.name.sans-serif.ko", "Droid Sans Fallback");

In my phone, it works nicely on web page. But, about:config screen is still bold styled.

Comment 2

[Channy Yun [:channy]]

Attachment: font styled bold in about:config

Comment 3

[Makoto Kato [:m_kato]]

There is no Korean font in default android environment, so we don't set correct font name in prefs.js yet.

Channy, what korean font does Samsung or LG install?  We should add it to name-list.

Comment 4

[Channy Yun [:channy]]

(In reply to Makoto Kato from comment #3)
> There is no Korean font in default android environment, so we don't set
> correct font name in prefs.js yet.
> 
> Channy, what korean font does Samsung or LG install?  We should add it to
> name-list.

I think that is not good to assign font name for each devices. In first, it's better to add values in mobile-l10n.js. 

- pref("font.name.sans-serif.ko", "Droid Sans");
+ pref("font.name.sans-serif.ko", "Droid Sans Fallback");

Comment 5

[Channy Yun [:channy]]

Attachment: font fallback for Korean

Comment 6

[Axel Hecht [:Pike]]

I'm not sure I like changing fonts just per locale.

Also, this wouldn't help the multi-locale builds, which now contain Korean.

Comment 7

[Channy Yun [:channy]]

(In reply to Axel Hecht [:Pike] from comment #6)
> I'm not sure I like changing fonts just per locale.
> 
> Also, this wouldn't help the multi-locale builds, which now contain Korean.

Okay. Makato, can you add this setting in https://hg.mozilla.org/releases/mozilla-aurora/file/0984ec812496/modules/libpref/src/init/all.js#l2809 ?

- pref("font.name.sans-serif.ko", "Droid Sans");
+ pref("font.name.sans-serif.ko", "Droid Sans Fallback");

Comment 8

[Makoto Kato [:m_kato]]

(In reply to Channy Yun from comment #7)
> (In reply to Axel Hecht [:Pike] from comment #6)
> > I'm not sure I like changing fonts just per locale.
> > 
> > Also, this wouldn't help the multi-locale builds, which now contain Korean.
> 
> Okay. Makato, can you add this setting in
> https://hg.mozilla.org/releases/mozilla-aurora/file/0984ec812496/modules/
> libpref/src/init/all.js#l2809 ?
> 
> - pref("font.name.sans-serif.ko", "Droid Sans");
> + pref("font.name.sans-serif.ko", "Droid Sans Fallback");

We should use font.name-list.sans-serif.ko instead of.

Comment 9

[Makoto Kato [:m_kato]]

Attachment: fix v1

Comment 10

[Channy Yun [:channy]]

(In reply to Makoto Kato from comment #9)
> Created attachment 633937 [details] [diff] [review]
> fix v1

By my test, pref("font.name-list.sans-serif.ko", "Droid Sans Fallback"); is not working. Instead of, pref("font.name.sans-serif.ko", "Droid Sans Korean"); is still working as like Japanese setting. I tested Samsung Galuxy S, SII and LG optimus phone.

Comment 11

[John Daggett (:jtd)]

Looks good but I think 'Droid Sans' should be at the head of the list.  This should fix the bug but improve perf for cases where the 'Droid Sans' case includes support for Korean.  Given that makers seem to enjoy messing around with default fonts, I think that's definitely possible.

Comment 12

[Channy Yun [:channy]]

(In reply to John Daggett (:jtd) (Away 15-22 June) from comment #11)
> Looks good but I think 'Droid Sans' should be at the head of the list.  This
> should fix the bug but improve perf for cases where the 'Droid Sans' case
> includes support for Korean.  Given that makers seem to enjoy messing around
> with default fonts, I think that's definitely possible.

Unfortunately, this patch cannot solve this problem. (You have to test in Korean version). According to my survery, Droid Sans Fallback(.ttf) is original Korean font.

Comment 13

[John Daggett (:jtd)]

Fallback uses all fonts in the font.name-list.xxx pref, so it will pick up Droid Sans Fallback if the characters are missing from Droid Sans.  But Droid Sans Fallback is a large font, it's always more optimal to use Droid Sans instead if possible.  Including it will *not* break the fix, it will merely insure that if a Korean maker includes glyphs for Korean in Droid Sans that we will pick that up instead.

Comment 14

[Channy Yun [:channy]]

Attachment: Serif as default font on Galuxy Tab

Another strange thing is that default font on galaxy tab 8.9 is still Serif type(Batang-che) despite of setting sans-serif as a default.

Comment 15

[Channy Yun [:channy]]

Jungshik, would you check this bug on Android?

Comment 16

[Channy Yun [:channy]]

Makoto Kato's patch is working only serif font for Galuxy Note and Tab. It changes serif font to sans-serif font as a default. But, primary problem is solved only by to change font.name.sans-serif.ko to Droid Sans Fallback.

Comment 17

[Jinkyu Yi[:jincreator]]

Hi!
I was so suprised about this bug, because I never meet with this bug - from nightly to stable!
I'm using Nexus S with ICS(4.0.4) and tested ko locale both Android and Firefox.
Here I attached screenshot with latest Aurora at now.

Comment 18

[Jinkyu Yi[:jincreator]]

Attachment: Korean letters shown correctly.

about:config in Firefox for Android Aurora(15.0a2 2012-06-26).
The letters are not bold.

Comment 19

[Jinkyu Yi[:jincreator]]

In Channy's screenshot, seems it doesn't use Droid Sans series, but I'm not sure.
I think Galaxy S2's different font set makes this problem.

Comment 20

[Makoto Kato [:m_kato]]

Attachment: fix v2

Although it isn't good way to add Droid Sans Fallback to font.name-sans-serif.ko, it is no way except to this, according to test result.

If feature version of Android adds korean font, we should modify this prefs.

Comment 21

[Makoto Kato [:m_kato]]

Attachment: fix v3

Comment 22

[John Daggett (:jtd)]

Comment on attachment 637779 [details] [diff] [review]
fix v3

> +// Droid Sans Korean is nothing, but this is dummy
> +pref("font.name.sans-serif.ko", "Droid Sans Korean");

I think you mean "Droid Sans Korean may not be present"

> +pref("font.name-list.sans-serif.ko", "Roboto, Droid Sans, Droid Sans Fallback");

You should include "Droid Sans Korean" here too.

r+ with changes

Comment 23

[Channy Yun [:channy]]

(In reply to John Daggett (:jtd) from comment #22)
> Comment on attachment 637779 [details] [diff] [review]
> fix v3
> 
> > +// Droid Sans Korean is nothing, but this is dummy
> > +pref("font.name.sans-serif.ko", "Droid Sans Korean");
> 
> I think you mean "Droid Sans Korean may not be present"
> 
> > +pref("font.name-list.sans-serif.ko", "Roboto, Droid Sans, Droid Sans Fallback");
> 
> You should include "Droid Sans Korean" here too.
> 
> r+ with changes

I did tests with this setting in Galuxy S, S2, Galuxy Note, but the problem is not fixed. I guess Droid Sans font has only bold type characters. (This setting means that only missing characters in Droid Sans are referred to Droid Sans Fallback. It's not this problem.)

Comment 24

[Channy Yun [:channy]]

So, as following setting is working. Please consider it.

-pref("font.name-list.sans-serif.ko", "Roboto, Droid Sans, Droid Sans Fallback");
+pref("font.name-list.sans-serif.ko", "Roboto, Droid Sans Fallback, Droid Sans");

Comment 25

[Jinkyu Yi[:jincreator]]

(In reply to Channy Yun from comment #23)
> I guess Droid Sans font has only bold type characters.

That's not true. Droid Sans doesn't has any type of Korean characters, and Droid Sans Fallback only include regular type of Korean characters. I mean, there's no bold type of Korean characters in any Droid Sans. 

As a result, Fennec can NOT show bold-styled Korean character in Nexus series. Should I open new bug report about it?

Comment 26

[Channy Yun [:channy]]

(In reply to Channy Yun from comment #24)
> So, as following setting is working. Please consider it.
> 
> -pref("font.name-list.sans-serif.ko", "Roboto, Droid Sans, Droid Sans
> Fallback");
> +pref("font.name-list.sans-serif.ko", "Roboto, Droid Sans Fallback, Droid
> Sans");

How's going this bug?

Comment 27

[Jungshik Shin]

Droid Sans Fallback comes only in a single weight (regular) and that's the only font in Google's reference build that covers Korean character. So, it's very strange that Korean characters are in bold no matter what font pref entries you have. 

Anyway, I'd have something like this:

font.name.sans-serif.ko => Roboto 
font.name-list.sans-serif.ko => "Korean fonts shipped with Korean Android device manufactures" followed by 'Droid Sans Fallback'

That way, in the presence of better Korean fonts on Samsung Galaxy S* or other Android devices sold in Korea, one of them will be used instead of Droid Sans Fallback (whose Korean quality is not that great). 

BTW, Korean fonts listed before DSF should cover the full set of 11,172 syllables. Otheriwse, there would be a ransom note effect because some of characters can be picked up from Droid Sans Fallback.

Comment 28

[Jinkyu Yi[:jincreator]]

(In reply to Jungshik Shin from comment #27)
> Droid Sans Fallback comes only in a single weight (regular) and that's the
> only font in Google's reference build that covers Korean character. So, it's
> very strange that Korean characters are in bold no matter what font pref
> entries you have. 
It's true there is only regular Korean characters in Droid Sans Fallback. The reason Korean characters are styled bold is another Korean font by manufacturer is shown instead of Droid Sans Fallback.

Actually, styled bold is symptom only in Samsung's phones(I guess Helvetica S bold or Samsung Gothic bold is used instead of Droid Sans Fallback). Other phones not manufactured by Samsung(ex SKY) will show strange fonts. So I suggent to change title of bug report, Channy.

I think the best way is through out every font preference and just follow android system's font matching.

Comment 29

[dhunterz]

I want this.

add "Droad Sans Fallback" before "Droid Sans" to "font.name-list.sans-serif.x-unicode", not ".ko".

today, many korean website makes unicode, so only ".ko" is not insufficient.

Comment 30

[jaysee5]

Korean is not showing up bold on my 4.1.2 device, but they are showing up in some strange italic style. All my .ko and unicode settings are default. I will upload a screenshot of google's own homepage on my device. Android and Chrome browsers show up normal.

Comment 31

[jaysee5]

Attachment: Default Italics font

Font is showing up as italic by default

Comment 32

[Channy Yun [:channy]]

I tested as following major devices:
1) Samsung Galuxy S1, S2, S3, S4, GaluxyTab 10, Galuxy Note 1, 2
2) LG Optimus LTE, G, G Pro 

If your device has same problem, please test as following preferences.
pref("font.name.sans-serif.ko", "Droid Sans Korean");
pref("font.name-list.sans-serif.ko", "Open Sans, DroidSansFallback");

Comment 33

[Makoto Kato [:m_kato]]

(In reply to Channy Yun [:channy] from comment #32)
> I tested as following major devices:
> 1) Samsung Galuxy S1, S2, S3, S4, GaluxyTab 10, Galuxy Note 1, 2
> 2) LG Optimus LTE, G, G Pro 
> 
> If your device has same problem, please test as following preferences.
> pref("font.name.sans-serif.ko", "Droid Sans Korean");
> pref("font.name-list.sans-serif.ko", "Open Sans, DroidSansFallback");

Channy, we haved already add some font define sto prefs.js ("Droid Sans Fallback" and "NanumGothic" to Firefox 23 for Korean.

Could you test this on Firefox Nightly?

Comment 34

[Channy Yun [:channy]]

I tested several devices of the latest version and confirmed to be solved.