Closed Bug 185753 Opened 22 years ago Closed 19 years ago

Special characters like ä, ö, ' etc. change to �. This does not happen all the time.

Categories

(Core :: Internationalization, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: kheikkil, Assigned: jshin1987)

References

()

Details

(Keywords: intl)

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130

In the page at
http://firingsquad.gamers.com/hardware/all_in_wonder_9700_pro_review/page19.asp ,
special character " changes to �.


Reproducible: Sometimes

Steps to Reproduce:
1. Install Mozilla 1.2.1 / 1.1 to the Windows 2000 SP3, default installation
2. Use it some time and then special characters change to � character.
3.

Actual Results:  
Special characters change to � character.

Expected Results:  
Special characters should be ", ä, ö, etc.
wfm
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Component: Localization → Internationalization
Resolution: --- → WORKSFORME
It also works for me if I open new browser (not just navigator window). When I
use the same browser longer then special characters start to change �
characters. Example from the page source code before and after:

Even if you don’t wish to integrate your PC with your home theater, it’s hard
not to like the ALL-IN-WONDER 9700 PRO.

Even if you don�t wish to integrate your PC with your home theater, it�s hard
not to like the ALL-IN-WONDER 9700 PRO.

Same happens with multiple internet sites and pages.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
It works for me on 12-16 trunk build.

Reporter:
Could you please clear the Cache (Edit | Preferences | Advanced | Cache), and
try again?

Since the page that mentioned here:
http://cn.rd.yahoo.com/home/3link2/?http://cn.sports.yahoo.com/
is a w/o charset meta-tag page, it could be affected by the browser default
charset or Cache.

I think you can correct it by clear the Cache or manually select charset as
western charset, and next time, when you visit the same page again, then the
page will be displayed fine.
Keywords: intl
I cleared the cache (memory and disk), all cookies, page history and location bar.  
After these changes special characters still change to �.

My default character coding is Western (ISO-8559-1) and in languages for web
pages I have [en-us] [en] and [fi].
After you clear the Cache, can you try to exit the browser and relaunch again?
or manually select western charset to reset.

Change to i18n default engineer. Simon, feel free to reassign.

Btw, the url in comment #3 was wrong, the url that I meant was:
http://firingsquad.gamers.com/hardware/all_in_wonder_9700_pro_review/page19.asp
Assignee: rchen → smontagu
Reassigning to ftang
Assignee: smontagu → ftang
If I exit the browser and relaunch it then special characters are ok. But when I
use the browser for a couple of hours then this same thing happens again.
Well, if you have never visited any page other than western charset, then I
believe the page will always display fine.  But if you happened visit a
non-western charset page, e.g. UTF-8 or whatever else, then Cache will remember,
this will help when you next time visit the same page.

The Cache will not affect to those pages w/ charset meta-tag.
Since the page that you mentioned:
http://firingsquad.gamers.com/hardware/all_in_wonder_9700_pro_review/page19.asp
is a w/o charset meta-tag page, so it will be affected by browser default
charset and Cache.

So you can either clear the Cache or manually select the correct charset or
maybe turn auto-detector ON, and visit that page again, then should be displayed
fine.

I think this is the expected behavior.  And this bug we can resolve as worksforme.
I visited http://cn.sports.yahoo.com/
and after that
http://firingsquad.gamers.com/hardware/all_in_wonder_9700_pro_review/page19.asp
everything was still ok. If I find out in which page these special characters
start to change I will try if I can reproduce this behaviour. Clearing cache or
manually changing the correct charset does not help.
This same "bug" is also in Mozilla 1.3a. Many users in Finland have this same
problem. With browsers like IE6, IE5, IE4, NS4.x this is not a problem. Only
thing that helps is to close and restart Mozilla. 
this sound like a bad bug. Estimate debugging time 2-5 days.
Blocks: 157673
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
what a hack. I have not touch mozilla code for 2 years. I didn't read these bugs
for 2 years. And they are still there. Just close them as won't fix to clean up.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago19 years ago
Resolution: --- → WONTFIX
Mass Reassign Please excuse the spam
Assignee: ftang → nobody
Mass Re-opening Bugs Frank Tang Closed on Wensday March 02 for no reason, all
the spam is his fault feel free to tar and feather him
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Reassigning Franks old bugs to Jungshik Shin for triage - Sorry for spam
Assignee: nobody → jshin1987
Status: REOPENED → NEW
All the problematic pages referenced are windows-1252 encoded pages that don't
define a charset.

Finish users must frequently be accessing those pages using a link from a page
that is using a non iso-8859-1 character set, and the defined behaviour of
mozilla in that case is to reuse the character set of the previous page, leading
to problems with all characters that are not 7 bit ASCII, as described or shown
in the attachment images.

The finish users should use universal autodetect to alleviate the problem. I
believe the finish localization is already setting it on by default, and we have
a bug opened to do the same for all versions, but are still waiting for fixes
for the problems with universal autodetect.

When the page is opened from a bookmark, the charset used is the one memorized
inside the bookmark entry.

If it is proved Mozilla uses a non standard charset for reasons other than the
one listed above, then describe precisely when and open another bug to fix the
occurence.

Resolved as INVALID.
Status: NEW → RESOLVED
Closed: 19 years ago19 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: