a lot of strange and random characters are shown




15 years ago
14 years ago


(Reporter: diego, Assigned: smontagu)



Firefox Tracking Flags

(Not tracked)




(4 attachments)



15 years ago
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7a) Gecko/20040127 Epiphany/1.1.5

the page at http://planet.gnome.org shows a lot of random characters with
strange characters, it happends in pages at random, sometimes after reloading
the page the strangeness disappears. The page given is a weblog aggregator, it
seems the characters are only incorrect near the same person weblog: rodrigo
moya, but in his weblog everything looks ok.

Reproducible: Sometimes
Steps to Reproduce:

attached are a screenshot and the source code for the page.

Comment 1

15 years ago
Created attachment 139983 [details]
screenshots showing the problem

Comment 2

15 years ago
Created attachment 139984 [details]
page saved by epiphany, it stores weired things

Comment 3

15 years ago
Created attachment 139985 [details]
page saved by links, this html is saved as it should

Comment 4

15 years ago
Created attachment 139986 [details]
configuration used to compile mozilla

Comment 5

15 years ago
Well, Rodrigo Moya's weblog is in ISO-8859-1 (without a charset declaration),
while http://planet.gnome.org is in UTF-8. Even in attachment 139985 [details], there are
some unrecognized characters that are displayed as ?. In attachment 139984 [details] it
looks as if the decoder isn't recovering from the errors somehow.

|ac_add_options --enable-native-uconv| in the config. might be the problem, but
there is no way that the page can be displayed correctly as it stands.
Assignee: nobody → smontagu
Component: Layout: Fonts and Text → Internationalization
QA Contact: core.layout.fonts-and-text → amyy

Comment 6

15 years ago
I agree with Simon. Either this bug has to be resolved as invalid or we have to
make our glue to 'native converters' better handle situations like this. 
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.