Bug 15319 - New CGFont backend returns 0 font extents
Summary: New CGFont backend returns 0 font extents
Status: RESOLVED FIXED
Alias: None
Product: cairo
Classification: Unclassified
Component: quartz font backend (show other bugs)
Version: 1.5.16
Hardware: Other All
: medium normal
Assignee: Carl Worth
QA Contact: cairo-bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-02 01:24 UTC by Richard Hult
Modified: 2008-04-02 23:37 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Test case (1.88 KB, text/plain)
2008-04-02 01:26 UTC, Richard Hult
Details
Build fix (581 bytes, patch)
2008-04-02 23:34 UTC, Richard Hult
Details | Splinter Review

Description Richard Hult 2008-04-02 01:24:29 UTC
The new backend returns 0 for font extents, will attach a short test case.

(Setting the atsui component, since there isn't one for the new one yet)
Comment 1 Richard Hult 2008-04-02 01:26:04 UTC
Created attachment 15626 [details]
Test case

The test case prints out the font extents height, which is 12 with the old backend and 0 with the new one.
Comment 2 Vladimir Vukicevic 2008-04-02 11:11:50 UTC
What OS version are you on?
Comment 3 Richard Hult 2008-04-02 11:13:23 UTC
I am on 10.5.2.
Comment 4 Vladimir Vukicevic 2008-04-02 11:16:01 UTC
Oh, the font extents!  Eek.  Fix coming today, I dunno how we don't have coverage of this in the test suite...
Comment 5 Vladimir Vukicevic 2008-04-02 16:14:42 UTC
Just pushed out a fix for this -- can you verify that it's working for you?
Comment 6 Richard Hult 2008-04-02 23:34:01 UTC
Created attachment 15638 [details] [review]
Build fix

It doesn't build, but with the small attached patch it seems to work fine, thanks!
Comment 7 Vladimir Vukicevic 2008-04-02 23:37:45 UTC
Bah, fixed that on my 10.4 machine but didn't push it to the 10.5 machine I checked in from.  Pushed out the fix.  thanks!


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.