Katsuhiko Momoi Reporter
	Description • 26 years ago

** Observed with 6/3/99 Win32 build running on Win95-J machine **

I noticed this problem on the Netscape Home Page  where you see many instances of the Katakana/Hiragana
long vowel symbol (\u30FC). Instead of the usual elongated shape, I see instead what looks to be
a 90 degrees rotated version of  bold right-bracket (\u3011). Two other symbols which seem to be wrong are
\u30FD and \u30FE. (If you happen to have these kinds of fonts at the top of your list, you can see its
effect by visiting the test page URL above also.)

As near as I can tell, this seems to be due to the fact that on my Win 95-J system, the top 2 fonts on the list
list are the ones from JustSystem's Ichitaro Word Processor installation, i.e. "$JS Gothic" and "$JS Mincho".

So this bug is a reminder that there needs to be a general/overall solution to font selection in drawing.

	Erik van der Poel Assignee
	Comment 1 • 26 years ago

*** Bug 7584 has been marked as a duplicate of this bug. ***

	Erik van der Poel Assignee
	Comment 2 • 26 years ago

Matt said that font prefs would be completed by M9, so I'm setting this to M9.

	Erik van der Poel Assignee
	Comment 3 • 25 years ago

First we will do font prefs, then we will add good defaults, which should fix
this problem. Marking M12.

	bobj
	Comment 4 • 25 years ago

Adding dependency on bug 8801 "[BETA] font prefs: ..."

	Erik van der Poel Assignee
	Comment 5 • 25 years ago

Kat, could you test this with the new font prefs? Try something like the
following in your own prefs file:

  user_pref("font.name.serif.ja", "MS Gothic");

	Erik van der Poel Assignee
	Comment 6 • 25 years ago

I checked in a fix to get non-ASCII font names to work in the prefs file on
Windows. We still need to add good default fonts to the default prefs files,
but I will leave that to bug 8801, so I'm marking this bug a dup of 8801.

*** This bug has been marked as a duplicate of 8801 ***

	bobj
	Comment 7 • 25 years ago

We need a spec on which font names/sizes to use in the default pref.js
files to use for the various platform/locale combinations.
I assume we can reuse the defaults from 4.x.  msanz?

	msanz
	Comment 8 • 25 years ago

Yes, use the same as in 4.x, we never had any complaint about it.

	Teruko Kobayashi
	Comment 9 • 25 years ago

Verified as dup.