Bug 161239 (cz_chars_bad)

Some characters with diacritics are displayed as character followed by (

RESOLVED WORKSFORME

Status

RESOLVED WORKSFORME
17 years ago
14 years ago

People

(Reporter: rfilipsk, Assigned: samir_bugzilla)

Tracking

Trunk
x86
Linux

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

17 years ago
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020529
BuildID:    2002052918

There are these characters: z with caron and s with caron which get displayed as
z or s followed by (. All other characters with diacritics are displayed
correctly. It may be related to difference between ISO-Latin-2 and MS Windows
1250 where these two characters have different encodings. I had this problem
with Oracle server running Unicode some time ago :-) Curious enough, after
clicking the Reload button, the text is displayed correctly.

Reproducible: Always
Steps to Reproduce:
1.Navigate to suggested URL.
2.Check the text on page


Actual Results:  There are character z and s on the page followed by (. It is
wrong. When I try to copy paste the text here it displays fine. So I guess there
is a problem only with the initial display of the page.

Expected Results:  Display the z and s characters with caron.

Users not aware of this and users with slow connection might very probably find
this at least very annoying.
(Reporter)

Updated

17 years ago
Alias: cz_chars_bad
WFM, Linux 2002080508

Comment 2

17 years ago
WFM, NT 4, build 2002072104 (1.1b)

Reporter, can you try with a newer build ? We're *this* close to release Mozilla
1.1, and a lot has changed.

Comment 3

16 years ago
No response from the reporter to comment #2. The website for the sample URL is
also down. Resolving WFM based on previous comments. Roman, if you can reproduce
this using a current copy of mozilla, please feel free to reopen this report.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → WORKSFORME
Product: Core → Mozilla Application Suite
You need to log in before you can comment on or make changes to this bug.