Closed
Bug 165804
Opened 22 years ago
Closed 17 years ago
integrate Xft/FontConfig into the mozilla X font code
Categories
(Core :: Internationalization, enhancement)
Tracking
()
RESOLVED
DUPLICATE
of bug 126919
People
(Reporter: bstell, Assigned: bstell)
References
Details
(Keywords: intl)
Xft/FontConfig are new X font technologies and should be integrated into moz's font code.
Comment 1•22 years ago
|
||
depends on the license ... (we can't take GPL code)
Assignee | ||
Comment 2•22 years ago
|
||
The goal is to call the library functions not add the source to moz's CVS repository. Would this cause a GPL problem?
Comment 3•22 years ago
|
||
Fontconfig (and XFT2) is integrated into XFree86 which is an X11 style license isn't it? Looking at the COPYING file with fontconfig (the closest I could find to a license) at http://cvsweb.xfree86.org/cvsweb/xc/lib/fontconfig/COPYING it looks ok to use (there is no mention of the GPL). I recommend implementing fontconfig as it simplifies many issues relating to i18n and fonts as well as soon adopting the CSS selection model for fonts. Keith Packard also maintains a patched build of mozilla with fontconfig at http://www.fontconfig.org/
Assignee | ||
Comment 4•22 years ago
|
||
You may want to look at bug 126919 where the proposal is to only use Xft and not to integrate it with the existing code. Right now there are several features in the existing code that are not in Xft/FontConfig (AASB, MathML, etc.) so that plan will cause regressions.
Comment 5•17 years ago
|
||
Fixed in bug 126919, but trunk now uses Pango (with cairo).
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•