Closed Bug 349469 Opened 18 years ago Closed 18 years ago

font-family alternatives not used (Win32)

Categories

(Core :: Graphics, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

VERIFIED INVALID

People

(Reporter: Mook, Unassigned)

Details

Attachments

(1 file)

User-Agent String:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060820 Minefield/3.0a1
This bug only appears on Win32/Cairo (not Win32/non-Cairo, nor Linux/Cairo)

Steps to reproduce:
Open attached testcase

Expected results:
Both lines are in Symbol font (Greek alphabet)

Actual results:
First line is in default font and does not match the second line

(If your system does not have Symbol as a font, use something else... fallback doesn't work with any font)

As far as I can tell, this is not quite bug 332649 nor bug 342466 (but then again I don't know any font code)
Attached file testcase (deleted) —
your testcase doesn't work at all in 1.5.  the problem with this on the trunk is that the windows font mapper will find us something for NotARealFontNamePlease based on the characteristics of the font we ask for (size, weight, etc) and that font will support the characters you've asked for.  I've tried forcing us to only load fonts that match by name, but we end up doing the wrong thing _a lot_ if we do that.  Not really sure what to do here.
I think that we should not use symbol font in this case. Because we don't support this using. That is supported only with <font face="">. I think that this bug should be marked to INVA, but we have the bug in font switching.
I'm marking this to INVA.

But I separated to two bugs they are found by this report.
1. When the non-existing font family is specified, the font specify is broken:
     I reported this in bug 352174.
2. We should not apply symbol fonts by CSS.(but should allow to specify by <font face="symbol">.
     I reported this in bug 352177.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
Thanks, it looks like I actually wanted bug 352174 but had an unfortunate test case :)

I should have used Comic Sans MS instead... :p (And yes, CJK Windows here - CP950/zh-TW)
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: