265235 - Strange font characters (look at paragraph TRUUS DRUYTS)

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[bart.kennes]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10.1

Na ‘Wittekerke’ breide ze de reportages in ‘Liefde, Lijf & Lust’ (VT4)
aan elkaar en spitte ze in het privéleven van zo'n 300 ‘Koppels’ (VT4).

Reproducible: Always
Steps to Reproduce:
1.
2.
3.



Expected Results:  
IE doesn't show these strange characters in the same webpage

Comment 1

[Peter van der Woude [:Peter6]]

Somehow Firefox does not allways get the right Character encoding.
I loaded the page a few times and didn't see your the problem.
Untill there's a way to actually reproduce the problem we're stuck with it.

Go to View->Character encoding->set Western (ISO-8859-1) manually to properly
display the page

Comment 2

[Jo Hermans]

<grin>I got a weak spot for Truusje too</grin>

Works for me in exactly the same version, also on Windows 2000, using the
universal auto-detector :
Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20040913 Firefox/0.10.1

The page is in ISO-8859-1 encoding, what you're reporting is often seen when the
text is send in UTF-8. Reporter, what encoding is used in your browser ? (see
View->Character Encoding, which one has a bullet in front ?) Are you using the 
'univeral' autodetector ? (which can sometimes make a mistake and select an
incorrect charset)

Comment 3

[bart.kennes]

(In reply to comment #2)
> <grin>I got a weak spot for Truusje too</grin>
> 
> Works for me in exactly the same version, also on Windows 2000, using the
> universal auto-detector :
> Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20040913 Firefox/0.10.1
> 
> The page is in ISO-8859-1 encoding, what you're reporting is often seen when the
> text is send in UTF-8. Reporter, what encoding is used in your browser ? (see
> View->Character Encoding, which one has a bullet in front ?) Are you using the 
> 'univeral' autodetector ? (which can sometimes make a mistake and select an
> incorrect charset)

(In reply to comment #2)
> <grin>I got a weak spot for Truusje too</grin>
> 
> Works for me in exactly the same version, also on Windows 2000, using the
> universal auto-detector :
> Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20040913 Firefox/0.10.1
> 
> The page is in ISO-8859-1 encoding, what you're reporting is often seen when the
> text is send in UTF-8. Reporter, what encoding is used in your browser ? (see
> View->Character Encoding, which one has a bullet in front ?) Are you using the 
> 'univeral' autodetector ? (which can sometimes make a mistake and select an
> incorrect charset)

The auto-detect function in the character encoding was default set at 'off'.
I changed it to univeral. Doing this it changed also automatically from Western
to Unicode. Truusjes paragraph is now displayed without font problems. Thnaks
for the support guys. Great work !

Comment 4

[bart.kennes]

(In reply to comment #3)
> (In reply to comment #2)
> > <grin>I got a weak spot for Truusje too</grin>
> > 
> > Works for me in exactly the same version, also on Windows 2000, using the
> > universal auto-detector :
> > Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20040913 Firefox/0.10.1
> > 
> > The page is in ISO-8859-1 encoding, what you're reporting is often seen when the
> > text is send in UTF-8. Reporter, what encoding is used in your browser ? (see
> > View->Character Encoding, which one has a bullet in front ?) Are you using the 
> > 'univeral' autodetector ? (which can sometimes make a mistake and select an
> > incorrect charset)
> 
> (In reply to comment #2)
> > <grin>I got a weak spot for Truusje too</grin>
> > 
> > Works for me in exactly the same version, also on Windows 2000, using the
> > universal auto-detector :
> > Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20040913 Firefox/0.10.1
> > 
> > The page is in ISO-8859-1 encoding, what you're reporting is often seen when the
> > text is send in UTF-8. Reporter, what encoding is used in your browser ? (see
> > View->Character Encoding, which one has a bullet in front ?) Are you using the 
> > 'univeral' autodetector ? (which can sometimes make a mistake and select an
> > incorrect charset)

>>>> 

> The auto-detect function in the character encoding was default set at 'off'.
> I changed it to univeral. Doing this it changed also automatically from Western
> to Unicode. Truusjes paragraph is now displayed without font problems. Thanks
> for the support guys. Great work !

Comment 5

[Gervase Markham [:gerv]]

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/

Comment 6

[Gervase Markham [:gerv]]

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.