165804 - integrate Xft/FontConfig into the mozilla X font code

Status: RESOLVED DUPLICATE of bug 126919

(Core :: Internationalization, enhancement)

Description

[kill this account]

Xft/FontConfig are new X font technologies and should be integrated into moz's
font code.

Comment 1

[Jo Hermans]

depends on the license ... (we can't take GPL code)

Comment 2

[kill this account]

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

[Michael Twomey]

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/

Comment 4

[kill this account]

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

[Karl Tomlinson (:karlt back Feb 10)]

Fixed in bug 126919, but trunk now uses Pango (with cairo).