265015 - Representation error of special characters and umlauts in coorperation with font administration software

Status: RESOLVED INCOMPLETE

(Core :: Layout: Text and Fonts, defect)

Description

[Marco Feltmann]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; de-DE; rv:1.7) Gecko/20040803 Firefox/0.9.3
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; de-DE; rv:1.7) Gecko/20040803 Firefox/0.9.3

When using the font administration software 'Extensis Suitcase X1' on an Mac OS
X system and administrating the system fonts using this tool, every line
containing umlauts or special characters is displayed in another font than the
other lines.

(look http://img30.exs.cx/img30/8393/firefox.png)

Reproducible: Always
Steps to Reproduce:
1. install suitcase x1
2. use 'administrate system fonts'
3. select all system fonts
4. activate them
Actual Results:  
show this lines in the incorrect system font

Expected Results:  
show this lines in the correct system font

Comment 1

[Marco Feltmann]

This error does only appear, if Suitcase does administrate the system fonts and
the font of the text isn't declared by css or the <font>-tag.

I've got these errors using 

Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; de-DE; rv:1.7) Gecko/20040628
Firefox/0.9.1

Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; de-DE; rv:1.7.3) Gecko/20041016
Firefox/1.0 (MMx)

Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; rv:1.7.3) Gecko/20041001
Firefox/0.10.1

Comment 2

[Marco Feltmann]

Also tested on 

Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; de-DE; rv:1.7) Gecko/20040803
Firefox/0.9.3

all the same.

Comment 3

[Martin Creutziger [:MMx]]

I think I can confirm that this is a bug.
The main question remains: How is this behaviour triggered?

Comment 4

[Martin Creutziger [:MMx]]

*** Bug 265017 has been marked as a duplicate of this bug. ***

Comment 5

[Boris Zbarsky [:bzbarsky]]

Is this only an issue on Mac?  If so, it's likely a Mac GFX bug...

Comment 6

[Jonathan]

macOS moving not just from PowerPC to Intel, but now from Intel to ARM, and the screenshot being 404: Should this still be open?

Comment 7

[Jonathan Kew [:jfkthame]]

None of the software that may have been involved here is relevant any more.