78544 - CJK characters won't display correctly when change charset other than which was specified in Composer

Status: VERIFIED WORKSFORME

(Core :: Internationalization, defect)

Description

[Yuying Long]

CJK characters won't display correctly when change charset other than which was 
specified in Compose.

Build: 0430 Win32 trunk build on Win2k-Simp. Chinese.

Note it not reproduce on 6.01 Win32 RTM build but reproduce even on 02-15(M0.8) 
trunk build.
Not reproduce on 05-02 trunk build on Mac-Ja and Linux-Ja neither.

Steps to reproduce:
1. Launch browser and open Composer.
2. Create a CJK file that has charset with(e.g. Shift-JIS, GB2312, ...).
3. Click "Browser" to bring up a navigator page.

Result:
1. The page was loaded correctly.  However, if you change charset other than the 
charset which was set up in Composer, e.g. if you created a shift-jis page in 
Composer, when you load it on Browser, it will load correctly at first time with 
shift-jis, and then choose another charset like iso-8859-1 or EUC-KR, then the 
page still didn't get override by new charset, and then you do it again or 
re-load it, then the page get overrided.
2. If you change back to correct charset from previous wrong charset, the first 
you still see the incorrect page, if you do it again or re-load it, then will 
get correct page.

Comment 1

[Yuying Long]

Add the keyword and change QA contact to me.

Comment 2

[Yuying Long]

Another steps to reproduce but not involved Composer:
Go: http://tw.yahoo.com.
   a. If the page was displayed correctly, then change charset to some other 
incorrect charset (e.g. ISO-8859-1, Shift-JIS,....), you will see the page still 
keep display correctly page(if you looking carefully, you will find it seems 
loading to differntly then change back as before), then change the incorrect 
charset again, this time you will get a display garbled page.
   b. If the page was displayed incorrectly, then change charset to Big5, the 
page didn't get display correctly, then you set charset to Big5 again to reload 
it, will get display fine page.  Now if you repeat step a, will get same result 
as above.

Comment 3

[Shanjian Li]

Yuying, can you find out when did this regression begin to happen?

Comment 4

[Yuying Long]

As I added in first comments, in Composer, it happens even on 02-15 trunk build 
but not on 6.01 RTM. The real page in Browser seems works fine till before 
05-02.  I can not find any build between 6.01 RTM and 02-15 on sweetlou.
Started on 05-02, I found real site http://tw.yahoo.com has same problem, and 
05-07 I found more CJK sites(e.g. http://www.asahi.com) have this problem too.
  

Comment 5

[Shanjian Li]

The problem seems like a layout/frontend problem. Document/parser/content seem fine. 
For example, after tw.yahoo.com is loaded (using big5) correctly, choose gb2312 does 
not seem to work. But if yo scroll down and back again, the whole page is displayed 
in gb2312.

Another observation might help detect the problem. Each time charset is switched, the 
right charset is flashed once and then goes back to old charset. It seems like we still
have the old frame model or copy of the display. 

Comment 6

[Shanjian Li]

I updated my tree today and this problem can no longer be seen. I am pretty sure the 
problem is not of i18n/document encoding/parser area. Because I do not know how it 
get fixed, I am afraid it might happen in future. I will mark this one as worksforme.
Please keep eyes on this one. 

Comment 7

[Yuying Long]

Verified not reproduce on 08-24 trunk build.