Closed Bug 54748 Opened 25 years ago Closed 24 years ago

Bogus default font settings for non-Latin languages

Categories

(Core :: Internationalization, defect, P3)

All
Other
defect

Tracking

()

VERIFIED FIXED
mozilla0.9

People

(Reporter: bobj, Assigned: jbetak)

Details

(Build 2000092808 on US Win95.) When you first open the font prefs dialog, Edit|Preferences...|Fonts, all encodings default to Times New Roman, Arial and Courier, even CJK language encodings. If you select an appropriate font (e.g., MS Gothic for Japanese), the drop down does now show Times New Roman other inappropriate fonts. The default should show the first Japanese font that is internally enumerated for Japanese.
By the way, Bob is using US Win95, and our default Japanese font is in Japanese, but US Windows uses the English font name. Accepting bug, for Future. Please nominate for RTM, if desired.
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Changed QA contact to ylong@netscape.com.
QA Contact: teruko → ylong
remove Future and reassign to nhotta.
Assignee: erik → nhotta
Status: ASSIGNED → NEW
Target Milestone: Future → ---
ylong, please check if this still happens.
I cannot reproduce with 6.0 RTM (win32).
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Verified it doesn't exist in 01-22 Mtrunk build too.
Status: RESOLVED → VERIFIED
Using 6.0 RTM on US Win95, the first time I look at the font for a non-Western language, it shows the same font selections currently selected for Western (e.g., Times New Roman). If I try a second time before closing the font pref dialog, then it shows a font that matches the language (e.g., Arial Unicode).
Status: VERIFIED → REOPENED
Resolution: WORKSFORME → ---
For my Mac US system with foreign language pack, in RTMja, when first time I look at the font for a non-Western language(e.g., Japanese, Chinese, ...), it Doesn't shows the same font selections currently selected for Western.
Marking as Future, first time only for a new profile, does not happen with JA RTM.
Status: REOPENED → ASSIGNED
Target Milestone: --- → Future
Reassign to jbetak.
Assignee: nhotta → jbetak
Status: ASSIGNED → NEW
accepting...
Status: NEW → ASSIGNED
Target Milestone: Future → mozilla0.9
works as of 04/05/2001
Status: ASSIGNED → RESOLVED
Closed: 25 years ago24 years ago
Resolution: --- → FIXED
Fixed verified on 04-05 trunk build.
Status: RESOLVED → VERIFIED
Reopening. Ran trunk build 2001040404 on US Win95. 1. Opened the Edit|Preferences... 2. Clicked on Appearance|Fonts 3. Opened the Language Encoding dropdown and click once on any of the languages 4. Each showed Times New Roman, Arial & Courier selected for Serif, Sans Serif & Monospace respectively 5. Clicked a second time on these language choices: Japanese, Traditional Chinese, Simplified Chinese, Korean, Thai, Hebrew or Arabic. The selected fonts for Serif, Sans Serif & Monospace showed as blank. I expected to see the default enumerated font. 6. Clicked a second time on the other the language choices. For these, the fonts selected remained the same as in (4.) This seems incorrect for some of these languages. Does Times New Roman really cover Baltic, Turkish etc.? Also the font choices offered for Unicode is very long and I'd expect it to only show fonts with a wide range of Unicode.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Additionally, when I closed the pref dialog and reopened it, I could repeat this behavior. It was not limited to just the first time in a new profile.
Bob, are you using 04-04 or 04-05 trunk build? because I believe the fix has been checked in yesterday(04-04) afternoon.
Sorry, I did not read the previous comments carefully. I ran the 4/4 trunk build (2001040404). The 4/5 build crashes on launch for me. I'll try again with tomorrow's build...
Clarifying previous comment -- The 4/5 build crashes after selecting my current profile and clicking on the Start Netscape 6 button (not immediately after launching).
so this is fixed
Status: REOPENED → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → FIXED
Yes, this is fixed. I verified with today's 4/6 trunk build, 2001040604.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.