161764 - UTF-8 default font set to western even on a Chinese window

Status: RESOLVED WONTFIX

(Core :: Internationalization, defect)

Description

[Yuying Long]

Build: 08-07 branch build / WinXP-SC

Steps:
1. Load a JavaScript open window, doesn't matter specify the charset or not in
pop-up open window.
I have test cases:
http://babel/JavaScript_i18n/SimpChinese/OpenWindow/UTF-8.html
http://babel/JavaScript_i18n/SimpChinese/OpenWindow/gb2312.html
2. Click on one of the selections to get the open window.

Result:
The font in pop-up window is different than in html file, seems it was used by
some other font but Chinese font (both gb2312 and UTF-8 case). Also if the
pop-up window contains gb18030 characters, the font is different than others too.

Comment 1

[Yuying Long]

Attachment: screen shot for detail

GB2312 characters in pop-up window seems using wrong font.

Comment 2

[Niklas Dougherty]

Unicode has its own preferred font in the preferences. Since many general
Unicode fonts iclude CJK characters, Mozilla might use such a font instead of a
dedicated Chinese font.

It may also use several different fonts, depending on available glyphs (and time
required to locate these). You can prevent this from happening by using a style
sheet that defines what fonts you prefer.

I can't look at your test cases, since "babel" is not a valid domain. Expanding
to "babel.com" doesn't help.

Comment 3

[Yuying Long]

Yes, I think I found the problems, there are two:
1. it use UTF-8 font to display the pop-up window because the charset carry over
the parent UTF-8 encoding into pop-up window, and in my preferences UTF-8 font
is setting to western font, so that caused the problem.

When create a new profile, the UTF-8 default font sets to western font,
but if user are running on a CJK OS, I think we should default to system default
font to avoid this kind of prblem. 

2. When specified the pop-up window as a charset, e.g. gb2312 for my 2nd case,
the pop-up window ignore it, still using UTF-8 font instead of Chinese(gb2312)
font. 

Comment 4

[Frank Tang]

reassign to ftang

Comment 5

[Frank Tang]

assign

Comment 6

[sheng han]

I have a page generated by CGI Perl. It is well declared the charater in the
header of the page:
<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">

The page is comprised with Chinese font (big5 and gb2312), deutsch, english and
could be anything else. My Firefox is configured to use UTF-8 as default coding
type. But the displaying result of this page is very dissapointed, whenever the
page is shown up, its set to Western-8859-1, regardless my preference in the web
page and firefox default setting.

If I am correct, my situation is related to this bug.

Please let me know if you need a testcase/screenshot, etc..

Cheers

Comment 7

[sheng han]

flaging this bug to be resolved by 1.8a5. Agree?

Comment 8

[Andrew Schultz]

> flaging this bug to be resolved by 1.8a5. Agree?

only drivers can set block flags.  you can request them

Comment 9

[sheng han]

1, who is the driver?
2, this bug was assigned to ftang, why all in the suddent it was changed to new?
 

Comment 10

[Jungshik Shin]

(In reply to comment #6)
> I have a page generated by CGI Perl. It is well declared the charater in the
> header of the page:
> <meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">

>  whenever the
> page is shown up, its set to Western-8859-1, regardless my preference in the web
> page and firefox default setting.

Are you sure your web server doesn't emit 'Content-Type: text/html;
charset=ISO-8859-1'? Note that the HTTP header is given a higher priority than
meta tag?  Please, give me the URL of a page generated by your CGI and I'll tell
you what's wrong with that. 
 
> If I am correct, my situation is related to this bug.
No, it's not !

Comment 11

[sheng han]

thanks for your reply Jungshik Shin,

the web page is located within a LAN, not accessible from outside.

however in my cgi, before printing anything, this line is printed at the top:
  print "Content-type: text/html;charset=UTF-8\n\n";

and inside the web page charset is set again in meta section.
The result? Still, the character is not displayed correctly, and Character
Encoding of Firefox (and Mozilla) is always set to Western ISO-8859-1 regardless
my preference in the code.


No matter if this bug is directly related to my problem or not, I would like to 
see it be fixed soon.

Comment 12

[Henri Sivonen (:hsivonen)]

Intentionally not inheriting stuff like this across window.open.