266848 - On the first launch of Camino, accentuated words are shown in an incorrect font

Status: VERIFIED WORKSFORME

(Camino Graveyard :: Page Layout, defect)

Description

[Matthieu Beaumel]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.2) Gecko/20040825 Camino/0.8.1
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.2) Gecko/20040825 Camino/0.8.1

On the first launch of Camino after a reboot, words containing accentuated
letters are shown in a different font than the others. Closing and launching
again Camino fixes this behaviour.

See the attached pictures for more information.

Reproducible: Always
Steps to Reproduce:

Comment 1

[Matthieu Beaumel]

Attachment: Camino displaying www.google.fr on the first launch

Notice how "Actualités", "Recherche avancée", Préférences", "Publicité" and "À
propos de Google" are displayed.

Comment 2

[Matthieu Beaumel]

Attachment: Camino displaying www.google.fr on the second launch

Notice how "Actualités", "Recherche avancée", Préférences", "Publicité" and "À
propos de Google" are displayed. This time, they use the same font as the other
regular text.
The "Nombre de pages Web recensées par Google..." line also seems to be
affected.

Comment 3

[Samuel Sidler (old account; do not CC)]

Is this on the *very* first launch of a new install (new profile as well)? Can
you go through all of the steps to reproduce this. Include what version of OS X
you're running as well as what locale you're using.

Comment 4

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

This looks like bug 239712, except it's just the words or lines with accented
characters that are not anti-aliased.

What are your sans-serif font preferences for Western European and Unicode?

Comment 5

[Simon Fraser [no longer active]]

Is this the automatic charset detector again?

Comment 6

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Google.fr declares:
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
when looking at view-source, so I would think that rules out the automatic
charset detector, no?

Er, but the W3C validator and grabbing the page with curl claim it's declaring:
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">

What!?

Comment 7

[Samuel Sidler (old account; do not CC)]

Matthieu, can you please update us with your configuration and status of this
bug? Is it fixed in 083? Is it fixed in a recent nightly? Please update.

Comment 8

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Does this problem still occur?  

I just rebooted, created a fresh Camino profile, launched Camino 2005092404
(v1.0a1+), and visited www.google.fr and everything appeared properly.

Comment 9

[Matthieu Beaumel]

Sorry for the delay.
I have conducted tests with the latest nightly and latest stable version (0.8.4). 
I could not reproduce anymore the behaviour. Seems it was fixed in the meantime.

Comment 10

[Samuel Sidler (old account; do not CC)]

Resolving WFM since it can't be reproduced by the reporter or triagers in a
recent build.

Please reopen if you see this again.