173114 - X11 font names are case-insensitive

Status: RESOLVED INCOMPLETE

(SeaMonkey :: General, defect)

Description

[Nicolas George]

Mozilla does not realize that the font "-Adobe-times-iso8859-1" from a TrueType
file and the font "-adobe-times-iso8859-1" provided by X11 are the same.
According to XLFD :

"Alphabetic case distinctions are allowed but are for human readability concerns
only.  Conforming X servers will perform matching on font name query or open
requests independent of case."

Comment 1

[Roland Mainz]

bstell:
What would I have to change here ?
Make |CompareFontNames()| and the regex code case-insensitive... something else
?!

Comment 2

[kill this account]

> Mozilla does not realize that the font "-Adobe-times-iso8859-1" from a TrueType
> file and the font "-adobe-times-iso8859-1" provided by X11 are the same.

I'm unclear what the issue here is. When would one form be use but the other
wanted?

Comment 3

[Roland Mainz]

Brian Stell wrote:
> > Mozilla does not realize that the font "-Adobe-times-iso8859-1" from a 
> > TrueType
> > file and the font "-adobe-times-iso8859-1" provided by X11 are the same.
>
> I'm unclear what the issue here is. When would one form be use but the other
> wanted?

If I understand the reporter correctly "-Adobe-Times-iso8859-1",
"-adobe-times-iso8859-1" and "-AdObB-TiMeS-iSo8859-1" should be all treated as
the same font.

Comment 4

[Tony Mechelynck [:tonymec]]

XLFD are not used by GTK2 IIUC -- instead of "-lucidatypewriter-medium-r-normal-*-*-90-°-°-m-*-*" it uses "Lucida Typewriter 9" (where I'm adding quotes for clarity only)

This would mean this bug has become INVALID. - Or am I mistaken?

Comment 5

[Robert Kaiser]

I regard this INCOMPLETE until we have data about it still happening on current cairo-based gtk2 builds (and then it wouldn't be SeaMonkey-specific any more).