freetz at gmx.net
Tue Oct 18 09:14:04 CEST 2005
--- "Patrys :: Patryk Zawadzki" <patrys at pld-linux.org> wrote:
> > > > it's because you added --disable-xft. it should be always enabled since
> > > > pango/gtk+ uses xft for font rendering.
> > >
> > > Actually not. It uses it internally. Mozilla developer docs explicitly
> > > say to always use --disable-xft when using --enable-pango.
> > Intresting information. Using a backend internally sound like
> > revolution to me ;)
> Read Mozilla docs. Mozilla can link directly against xft or against
> freetype2. This has nothing to do with the toolkit of choice as the
> canvas (the part where site content is rendered) is toolkit-independent.
I don't talk about GUI or canvas, but only about font rendering.
> Enable/disable xft/freetype2 has no impact on the rest of Fx GUI.
Breaking mozilla-firefox build is a big impact.
> > according to your ex-TODO:
> > # ac_add_options --enable-xft
> > # Enables XFT advanced font rendering. This is only available with
> > # --enable-default-toolkit=gtk2, and it is recommended with gtk2
> > ^^^^^^^^^^^^^^^^^^^^^
> > % grep toolkit= mozilla-firefox.spec
> > ac_add_options --enable-default-toolkit=gtk2
> > ^^^^
> > could you explain this?
> Read the whole thing:
> ac_add_options --enable-xft
> Enables XFT advanced font rendering. This is only available with
> --enable-default-toolkit=gtk2, and it is recommended with gtk2
> ac_add_options --enable-freetype2
> Enables freetype font rendering. This is the default for the GTK
> toolkit. Not compatible with --enable-xft
GTK = old gtk+ (1.2.x), gtk2 = gtk+2 (2.x.x)...
> Especially the "not compatible with" part. Full configure options
> description available at
Why should I read it? I don't have problems with undefined symbols and
I don't want to use deprecated pango X font backend.
More information about the pld-devel-en