We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Caută ajutor

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

Different font style for different character set

  • 2 răspunsuri
  • 2 au această problemă
  • 9 vizualizări
  • Ultimul răspuns de Kevin

Akihiro HARAI
Akihiro HARAI
more options

I am a Japanese user and I need a help about customizing font styles.

In Japanese writing system, original character sets like Kanji or Kana and alphabet are mingled together in one document. But in our publishing custom, each uses different font style when showing. For example, while using MS Mincho for Kanji and Kana, alphabet is displayed using Times New Roman, despite the fact that MS Mincho also has alphabetic characters in it!!

The problem is that Firefox for Mobile cannot do this kind of font choosing. As I have added a monospaced Japanese font called "MTLmr3m.ttf" (the default Japanese font in Jelly Bean) to /system/etc/fallback_fonts.xml, Firefox always shows monospaced dirty alphabet of the font set unless otherwise noted in stylesheet.

https://dl.dropbox.com/u/293467/firefox-font-problem/firefox.png

Of course, other browsers like Browser or Chrome can handle this correctly.

https://dl.dropbox.com/u/293467/firefox-font-problem/chrome.png

While I love Firefox and I want to read clear Japanese with the new font, it is not tolerable to see the dirty alphabet.

How can I solve this problem?

ACER ICONIA TAB A500 ROM: TegraOwners ICS v170 Firefox for Mobile 16.0.2

I am a Japanese user and I need a help about customizing font styles. In Japanese writing system, original character sets like Kanji or Kana and alphabet are mingled together in one document. But in our publishing custom, each uses different font style when showing. For example, while using MS Mincho for Kanji and Kana, alphabet is displayed using Times New Roman, despite the fact that MS Mincho also has alphabetic characters in it!! The problem is that Firefox for Mobile cannot do this kind of font choosing. As I have added a monospaced Japanese font called "MTLmr3m.ttf" (the default Japanese font in Jelly Bean) to /system/etc/fallback_fonts.xml, Firefox always shows monospaced dirty alphabet of the font set unless otherwise noted in stylesheet. https://dl.dropbox.com/u/293467/firefox-font-problem/firefox.png Of course, other browsers like Browser or Chrome can handle this correctly. https://dl.dropbox.com/u/293467/firefox-font-problem/chrome.png While I love Firefox and I want to read clear Japanese with the new font, it is not tolerable to see the dirty alphabet. How can I solve this problem? ACER ICONIA TAB A500 ROM: TegraOwners ICS v170 Firefox for Mobile 16.0.2

Toate răspunsurile (2)

Akihiro HARAI
Akihiro HARAI Deținătorul întrebării
more options

I solved this problem myself.

It is font.name-list.sans-serif.ja property in about:config that configure the precedence of font family applied to sans-serif style, which is the default font style of Firefox.

My default value of the property was MotoyaLMaru, MotoyaLCedar, Droid Sans Japanese. This means "apply Japanese font to every single character in web pages."

I changed it to Roboto, Droid Sans, MotoyaLMaru, MotoyaLCedar, Droid Sans Japanese, which means "use Roboto or Droid Sans if the character is supported by the font family; otherwise use Japanese font."

And everything works fine now.

Kevin
Kevin
  • Moderator
more options

I opened a bug about this for a more general solution. https://bugzilla.mozilla.org/show_bug.cgi?id=811201