Bug 82085

Summary: Mozilla Japanese font is very dirty
Product: [Retired] Red Hat Public Beta Reporter: Nakai <ynakai>
Component: mozillaAssignee: Christopher Blizzard <blizzard>
Status: CLOSED RAWHIDE QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: phoebeCC: eng-i18n-bugs, hp, otaylor, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-01-30 11:18:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 79578    
Attachments:
Description Flags
mozdirty.png none

Description Nakai 2003-01-17 09:49:53 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021218

Description of problem:
When I input Japanese string into html form with Mozilla,
it shows very dirty fonts.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Input Japanese string into http://www.google.com/ form with mozilla
2. Japanese 'aaaaa'
3. Dirty
    

Additional info:
Comment 1 Nakai 2003-01-17 09:53:05 UTC 
Created attachment 89418 [details]
mozdirty.png
Comment 2 Nakai 2003-01-17 09:55:02 UTC 
If Hiragana is in the string, it gets very dirty.
If not, the string gets antialiased.

That's very silly behavior.
Comment 3 Christopher Blizzard 2003-01-18 15:46:19 UTC 
That's all Xft.
Comment 4 Leon Ho 2003-01-28 03:07:18 UTC 
Look like it is getting two different fonts. Is mozilla just getting the first "suitable" 
font on the list?
Comment 5 Christopher Blizzard 2003-01-28 15:43:19 UTC 
Yes, that's what it does via the xft setup.
Comment 6 Owen Taylor 2003-01-28 16:08:32 UTC 
A) Perhaps Mozilla isn't setting the language tags for controls
   based on the language of the page? 

B) Does removing the fonts in /usr/share/fonts/ja/misc improve
   the situation?

C) Does removing bitmap-fonts-cjk improve the situation (if you
   have that installed?)
Comment 7 Leon Ho 2003-01-29 03:57:41 UTC 
> B) Does removing the fonts in /usr/share/fonts/ja/misc improve the situation? 
mv /usr/share/fonts/ja/misc /tmp; still the same 
 
> C) Does removing bitmap-fonts-cjk improve the situation (if you have that 
installed?) 
 
Same- However I have tested around on which fonts that effect the selections: *if* i 
remove console* in /usr/share/fonts/bitmap-fonts/ then the display and font 
selection will look much better (will only select ttf font so that we could not see the 
rendering problem of console glyphs). We may have two folds the problem - one 
may related to ways of only return a font with nearest to fullset of the charset. 
Another one is the rendering problem on the console font(?)
Comment 8 Christopher Blizzard 2003-01-29 15:42:39 UTC 
> A) Perhaps Mozilla isn't setting the language tags for controls
>    based on the language of the page? 

As far as I know, it is.
Comment 9 Nakai 2003-01-30 11:18:17 UTC 
Seems to be fixed in Phoebe4 + mozilla 1.2.1-15