36136 - [regression]View source with meta charset info does not display correct characters

Status: VERIFIED FIXED

(Core :: Internationalization, defect, P3)

Description

[Teruko Kobayashi]

When you see the source of other language page, the Page source window are not
displayed correct language even though the page has meta charset info.

Steps of reproduce
1. Go to above URL
2. Select menu View|Page source

Japanese characters are not displayed correctly in the Page source window.

Tested 2000041706 M15 Win32, Mac, and Linux and 2000041410 M16 Win32 build.

Comment 1

[Teruko Kobayashi]

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

Comment 2

[[e-mail] (away - not reading bugmail)]

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

Comment 3

[Phil Peterson]

[nsbeta2-]

Comment 4

[msanz]

teruko, can you change the charset info on the view menu? If you do so, does it 
display correctly? In other words, is there a workaround?

Comment 5

[[e-mail] (away - not reading bugmail)]

yes, there are two workarounds:

- Autodetect
- manual charset menu adjustment in the original HTML document
  (bug 32591, View source in no meta tag pages, has been fixed)

This problem occurs only, if the user didn't preset the charset menu and 
Autodetect is off. It happens due 
to the fact that view-source pages pass the "guts" of the client disguising 
themselves as XML documents. 
Here a comment from RickG: 

>------- Additional Comments From [e-mail] 2000-01-21 17:02 -------
>In my tree -- I've changed plaintext from using XML to being an HTML document. 
>ViewSource however is XML and will remain XML because of the additional 
>capabilities we expect to layer upon it.

This has led to a slew of problems (12502 , 28484 , 29758 , 32591, 23577,  
36136) and made a 
number of extensions and "hacks" neccessary. As far as I know, meta tag 
detection for XML documents 
has not yet been even considered, which makes the matters really bad.  Once 
there is some sort of 
additional framework in place for setting doc charsets from JS for bug 18022, as 
opposed to viewer or 
menu charsets, which can presently be done via the browser instance proxy, we 
could address this issue 
without touching the what I'd call "XML swamp".

Comment 6

[Charles Wang]

Observed on Mac 2000-05-18-10 comm build:

I think this problem is getting much better now. Before JA, Korean, Chinese were 
 all garbled and now turn to question marks. If adjust  charset menu 
manually,sometimes the page source displays fine. But after browsing around, the 
multiple checked marks bug 31104 comes in and affrects language convertor. 
Korean behaves better because it can be mannually adjusted at any time. 

Comment 7

[[e-mail] (away - not reading bugmail)]

view source is still broken for pages with meta tag. It worked in Beta1 though 
and was confirmed as PTD+ back then. This bug is a member of an interdependent 
"triplet"; getting nsbeta2+ for one of them would help us to take care of all 
three...

Comment 8

[leger]

Putting on [nsbeta2+] radar for beta2 fix. 

Comment 9

[leger]

Dogfood for International..putting on [dogfood+] radar.

Comment 10

[[e-mail] (away - not reading bugmail)]

OK, the fix is in - it should work in nightly builds beginning from 05/24/2000

Comment 11

[Teruko Kobayashi]

I verified this in 2000-05-08 Win32, Mac, and Linux build.