Closed
Bug 70091
Opened 23 years ago
Closed 23 years ago
Illegal font is used if specified "font-family: gothic"
Categories
(Core :: Internationalization, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: kazhik, Assigned: masaki.katakai)
Details
(Keywords: intl)
Attachments
(2 files)
Illegal font is used if "font-family: gothic" is specified for Japanese text.
Reporter | ||
Comment 1•23 years ago
|
||
a. Gothic is not a CSS2 generic font family name b. I have no font called Gothic on my system c. the attached test case is ok on 0.9.2 if character encoding set to japanese (attaching snapshot) reporter, can you please give more details about the bug ?
Comment 4•23 years ago
|
||
# This bug originated from http://bugzilla.mozilla.gr.jp/show_bug.cgi?id=704 The fonts used in attachment 40881 [details] are not Japanese(*-jisx0208.*-0). I think they are Chinese(*-gb2321.*-0) or Korean(*-ksc5601.*-0). Some glyphs in jisx0208, gb2321, ksc5601 have same codepoint in UCS2, so Mozilla must chose a correct (or proper) font(s). The hints are : 1. Character-Coding indicated by user 2. LANG attribute (in multilingual document?) 3. document charset written in the document header 4. charset auto detected 5. Auto-Detect Character-Coding indicated by user 6. Language or Default Character Coding pref 7. System setting? (LANG or locale) The attachment 26132 [details] is encoded by Shift_JIS, so font searching order must be: -*-gothic-...-jisx0208.1983-* -*-*-...-jisx0208.1983-* -*-gothic-...-*-* -*-*-...-*-* -------- Behavior in the original report (http://bugzilla.mozilla.gr.jp/show_bug.cgi?id=704) seems that the font for "font-family: gothic" is searched without the information about language (lang attribute nor document charset).
Assignee | ||
Comment 5•23 years ago
|
||
I believe this is dup of bug 83250 which has been already fixed in Trunk.
Comment 6•23 years ago
|
||
Reassigned to I18N / Masaki Katakai to confirm that this bug is fixed.
Assignee: pierre → katakai
Component: Style System → Internationalization
Assignee | ||
Comment 7•23 years ago
|
||
OK, This problem has been already fixed. Mark this as FIXED.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•