Closed
Bug 322938
Opened 19 years ago
Closed 18 years ago
turn on thebes/cairo as default rendering back end on all primary platforms
Categories
(Core :: Graphics, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: vlad, Assigned: vlad)
References
Details
(Whiteboard: [blocking1.9a1+])
This is the tracking bug for making thebes/cairo the default back-end for linux, windows, and mac. The current target for this is end of January (2006).
Assignee | ||
Updated•19 years ago
|
Flags: blocking1.9a1?
Comment 1•19 years ago
|
||
What's the plan for bug 305649? If I read that bug correctly, then this won't run or compile on default pretty much anything Linux (up through and including FC4).
Depends on: 305649
I'm not that worried about the "won't compile" case prior to our release of Fx3, since developers can install whatever versions they want in alternate locations, or update their systems appropriately. We should talk to Linux distro types and see what their plans are for providing pango updates to their supported distributions, for the start-of-2007 timeframe. Copying Blizzard here, who else?
Assignee | ||
Comment 3•19 years ago
|
||
There's no compilation issue any more, though there will most likely be performance issues on non-recent X servers that we'll have to work through. We're back to Pango 1.6 as the baseline, so it will compile and run on anything that's recognizable as modern linux.
Updated•19 years ago
|
Depends on: cairo-gtk2
Updated•18 years ago
|
Flags: blocking1.9a1? → blocking1.9+
Whiteboard: [blocking1.9a1+]
Assignee | ||
Updated•18 years ago
|
Assignee: nobody → vladimir
Updated•18 years ago
|
Summary: turn on thebes/cairo as default rendering back end → turn on thebes/cairo as default rendering back end on all primary platforms
Comment 5•18 years ago
|
||
<borat>Niiiice</borat>
Comment 7•17 years ago
|
||
Simon, Is the rendering problem of Pali (Classic Sinhala) related to this bug (fixed, of course) or different because it is essentially turning on Glyph Shaping for it though Pali is not a complex script being Latin-1 yet requires glyph rendering as the ligatures are in the OpenType Private area? Microsoft's example here is interesting: http://msdn2.microsoft.com/en-us/library/ms776501.aspx I wonder if that has some bearing to this problem? Or, am I totally in the dark on what is going on with Pali?
Assignee | ||
Comment 8•17 years ago
|
||
This is not even remotely the right bug for that question; please file a new bug for any issues with Pali.
Comment 9•17 years ago
|
||
(In reply to comment #7) > Simon, > Is the rendering problem of Pali (Classic Sinhala) related to this bug (fixed, > of course) or different because it is essentially turning on Glyph Shaping for > it though Pali is not a complex script being Latin-1 yet requires glyph > rendering as the ligatures are in the OpenType Private area? Turning on glyph shaping for Latin text is fixed by bug 387969. See http://kb.mozillazine.org/Browser.display.auto_quality_min_font_size
You need to log in
before you can comment on or make changes to this bug.
Description
•