Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 04 Dec 2003 02:03:20 -0500
From:      Joe Marcus Clarke <marcus@marcuscom.com>
To:        bernard.el-hagin@lido-tech.net
Cc:        FreeBSD User Questions List <freebsd-questions@freebsd.org>
Subject:   Re: Anti aliased fonts in FBSD
Message-ID:  <1070521400.26031.42.camel@shumai.marcuscom.com>
In-Reply-To: <klmtsvkr70fgbvd1hdfv6nuqv1m97mompj@4ax.com>
References:  <n9itsv0qitnivjqoeqlp08c5pculoui4ik@4ax.com> <1070518494.26031.21.camel@shumai.marcuscom.com> <78ktsvgnq7f5n98np0vkgkdtp2q4qrhn0v@4ax.com> <1070519258.26031.32.camel@shumai.marcuscom.com> <acltsvck8h49np1mdmmnv17iga4602fgbt@4ax.com> <1070520700.26031.39.camel@shumai.marcuscom.com> <klmtsvkr70fgbvd1hdfv6nuqv1m97mompj@4ax.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--=-lsW0AwIia1aw/Tzn4f6G
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Thu, 2003-12-04 at 01:58, Bernard El-Hagin wrote:
> owner-freebsd-questions@freebsd.org wrote:
>=20
> >On Thu, 2003-12-04 at 01:41, Bernard El-Hagin wrote:
> >> owner-freebsd-questions@freebsd.org wrote:
> >>=20
> >> >On Thu, 2003-12-04 at 01:17, Bernard El-Hagin wrote:
> >> >> owner-freebsd-questions@freebsd.org wrote:
> >> >>=20
> >> >> >On Thu, 2003-12-04 at 00:46, Bernard El-Hagin wrote:
> >> >> >> Hello,
> >> >> >>=20
> >> >> >>   When I install some appliactions from ports they have nice
> >> >> >> anti-aliased fonts by default (gaim, for example). Unfortunately=
 others
> >> >> >> do not (most notably gVim and also LinCVS, both of which are cap=
able of
> >> >> >> using them). Where exactly is this governed? How do I tell appli=
cations
> >> >> >> to always use anti-aliased fonts? I am running CURRENT.
> >> >> >
> >> >> >There's a section on this in the FreeBSD handbook:
> >> >> >
> >> >> >http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-fonts.=
html
> >> >>=20
> >> >>=20
> >> >> Thanks to that section of the handbook I have enabled anti-aliased =
fonts
> >> >> in X, but it doesn't explain why some applications use those fonts =
by
> >> >> default and others don't. That's my real problem.
> >> >
> >> >Yes it does.  The last paragraph states:
> >> >
> >> >"Anti-aliasing should be enabled the next time the X server is starte=
d.
> >> >However, programs must know how to take advantage of it. At present, =
the
> >> >Qt toolkit does, so the entire KDE environment can use anti-aliased
> >> >fonts (see Section 5.7.3.2 on KDE for details). Gtk+ and GNOME can al=
so
> >> >be made to use anti-aliasing via the ``Font'' capplet (see Section
> >> >5.7.1.3 for details). By default, Mozilla 1.2 and greater will
> >> >automatically use anti-aliasing. To disable this, rebuild Mozilla wit=
h
> >> >the -DWITHOUT_XFT flag."
> >> >
> >> >So, do you have gVim built with gtk+-2 support, and have you done wha=
t
> >> >section 5.7.3.2 tells you for KDE/Qt apps (i.e. set QT_XFT to true)?
> >>=20
> >>=20
> >> I don't use KDE nor Gnome, but as I understand it any application whic=
h
> >> is built with either Qt or Gtk+-2 support should be capable of using
> >> anti-aliased fonts. What I'm asking is how do I:
> >
> >Yes, per the cross-referenced sections in the above paragraph, you may
> >have to do some additional setting of variables if you do not use the
> >respective desktops.
> >
> >>=20
> >>=20
> >> 1. find out before building an application whether it will be built wi=
th
> >> support for either of those,
> >
> >As things are right now, looking at the ports' Makefiles is your best
> >bet.
>=20
>=20
> OK, that's what I was looking for. Thanks.
>=20
>=20
> >> 2. make sure that such support is added if it's not there by default
> >> (which I should be able to establish in step 1).
> >
> >Once you figure out the variable to set, you can add it to make.conf or
> >pkgtools.conf (or both).
>=20
>=20
> Does this mean that the name of the variable governing the AA fonts will
> be the same for any application which can use them? That's cool.

No.  WITH[OUT]_XFT is what some ports use, but some ports will use AA as
long as they're built with a supporting toolkit (e.g. vim).  In those
cases, you have to set the make variable to enable the port to build
with that toolkit (e.g. WITH_GTK2).

Joe

>=20
>=20
> Thanks for your help.
>=20
>=20
> Cheers,
> Bernard
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.o=
rg"
--=20
PGP Key : http://www.marcuscom.com/pgp.asc

--=-lsW0AwIia1aw/Tzn4f6G
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQA/ztw4b2iPiv4Uz4cRAii2AJ4t0TI16DrSefV6NDicW7zMCW2ZvACeMjoy
ZtXzDKtjkoQArrqNkfWt1LA=
=oKI3
-----END PGP SIGNATURE-----

--=-lsW0AwIia1aw/Tzn4f6G--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1070521400.26031.42.camel>