User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:184.108.40.206) Gecko/2008070208 Firefox/3.0.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:220.127.116.11) Gecko/2008070208 Firefox/3.0.1 The only way to get UTF8 coded Chinese pages to display properly in Firefox is to choose a Chinese font (Simsun, mssong) as the default font in Firefox. Otherwise half the entries are not seen. This is not a case of characters outside the range of unicode - these are common characters. Using Arial, Times New Roman, or another unicode font should display all of the characters. This makes coding a dual language page very difficult. Font definitions must be changed each time a Chinese character is entered. In my case, I simply remove the font face and allow default. Somehow that other browser solved the problem - it can use Arial and Times New Roman to display Chinese in UTF8 - so that those people who do not have their web browser properly set to display Chinese using Chinese fonts can still see it. It also seems to work better if the entire page is coded in html as one of the Western unicode fonts. Then I don't have to switch font coding on and off. Reproducible: Always Steps to Reproduce: 1. change font for Chinese under options to Arial, Times New Roman 2. look at Chinese UTF8 web page 3. now look at IE doing the same thing Actual Results: Chinese character disappear
This is a mass search for Firefox General bugs filed against version 3.0 that are UNCO and have not been changed for 200 days. Reporter, please update to Firefox 3.6.10 or alter. Firefox 3.0 is no longer supported and is no longer receiving updates. After you update, please create a fresh profile, http://support.mozilla.com/kb/managing+profiles, and test to see if your bug still exists. If you still the bug, then please post a comment with the version you tested against, and the problem. If the issue is no longer there, please set the RESOLUTION to RESOLVED, WORKSFORME.
No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.