Closed
Bug 277656
Opened 20 years ago
Closed 20 years ago
Update nsFontMetricsXft in Cairo
Categories
(Core Graveyard :: GFX, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jshin1987, Assigned: jshin1987)
Details
Attachments
(1 file)
28.00 KB,
patch
|
dbaron
:
review+
roc
:
superreview+
dbaron
:
approval-aviary1.1a1+
dbaron
:
approval1.8b2+
|
Details | Diff | Splinter Review |
There are a couple of changes to gtk/nsFontMetricsXft.cpp that haven't been
ported to cairo/nsFontMetricsXft.cpp. Among them are dbaron's fix for 'bad'
fonts and moving of some utility functions to shared/nsFontConfigUtils.
Updated•20 years ago
|
Summary: Update nsFontMetricsXft in Cairo → Update nsFontMetricsXft in Cairo
Comment 1•20 years ago
|
||
*** Bug 277659 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 2•20 years ago
|
||
Now that cairo build error was fixed, I made a patch porting all the changes
made in gtk/nsFontMetricsXft* (since the fork) to cairo-xft.
Assignee | ||
Comment 3•20 years ago
|
||
Comment on attachment 182233 [details] [diff] [review]
patch
asking for r/sr
this part of cairo-build went fine although it failed in content/.
Attachment #182233 -
Flags: superreview?(roc)
Attachment #182233 -
Flags: review?(dbaron)
Attachment #182233 -
Flags: review?(dbaron) → review+
In general we need to figure out how to integrate our font code with the
emerging Cairo font API.
Assignee | ||
Comment 5•20 years ago
|
||
(In reply to comment #4)
> In general we need to figure out how to integrate our font code with the
> emerging Cairo font API.
I have no doubt about that, but I'm not sure what you meant by that in the
context of this bug. Did you mean that it's not worth making nsFontMetricsXft in
cairo up to date with the one in gtk2 because it's gonna change drastically in
the near future?
Status: NEW → ASSIGNED
Comment on attachment 182233 [details] [diff] [review]
patch
It's worth keeping them in sync. I just wanted to make sure you don't do tons
of work to get this working really well before we change it drastically :-)
Attachment #182233 -
Flags: superreview?(roc) → superreview+
Assignee | ||
Comment 7•20 years ago
|
||
Comment on attachment 182233 [details] [diff] [review]
patch
Thanks for sr and clarification.
asking for a to trunk. this patch is for non-default cairo build so that it's
not critical to get this in before 1.8b2/1.1a. (provided that cairo wouldn't
have its heyday in 1.1).
On the other hand, this patch is just porting changes made in gtk/xft to
cairo/xft and little 'deliberation' by driver is necessary :-)
Attachment #182233 -
Flags: approval1.8b2?
Attachment #182233 -
Flags: approval-aviary1.1a?
Comment on attachment 182233 [details] [diff] [review]
patch
Most other checkins to gfx/src/cairo/ these days have been without approval,
which is fine, since it's not part of anything that's going to be relevant for
1.8/a1.1.
Attachment #182233 -
Flags: approval1.8b2?
Attachment #182233 -
Flags: approval1.8b2+
Attachment #182233 -
Flags: approval-aviary1.1a?
Attachment #182233 -
Flags: approval-aviary1.1a+
Assignee | ||
Comment 9•20 years ago
|
||
landed on the trunk
thanks for quick a and sorry for bothering you with unnecessary req.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Updated•16 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•