From owner-freebsd-questions@FreeBSD.ORG Wed Dec 3 22:43:26 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 15DB516A4D0 for ; Wed, 3 Dec 2003 22:43:26 -0800 (PST) Received: from airbus.lido-tech.net (airbus.lido-tech.net [62.89.127.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F1C643FBD for ; Wed, 3 Dec 2003 22:43:24 -0800 (PST) (envelope-from bernard.el-hagin@lido-tech.net) Received: from localhost (localhost [127.0.0.1]) by airbus.lido-tech.net (Postfix) with ESMTP id 9706624CDF for ; Thu, 4 Dec 2003 06:33:05 +0000 (GMT) Received: from airbus.lido-tech.net ([127.0.0.1]) by localhost (airbus [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 27378-03 for ; Thu, 4 Dec 2003 06:33:04 +0000 (GMT) Received: from lido-tech.net (domino01.lido-tech [192.168.32.82]) by airbus.lido-tech.net (Postfix) with ESMTP id A086A24C61 for ; Thu, 4 Dec 2003 06:33:04 +0000 (GMT) Received: from gdndev25.lido-tech ([192.168.38.25]) by lido-tech.net (Lotus Domino Release 5.0.11) with SMTP id 2003120407461274:40699 ; Thu, 4 Dec 2003 07:46:12 +0100 From: Bernard El-Hagin To: Date: Thu, 04 Dec 2003 07:41:27 +0100 Message-ID: References: <1070518494.26031.21.camel@shumai.marcuscom.com> <78ktsvgnq7f5n98np0vkgkdtp2q4qrhn0v@4ax.com> <1070519258.26031.32.camel@shumai.marcuscom.com> In-Reply-To: <1070519258.26031.32.camel@shumai.marcuscom.com> X-Mailer: Forte Agent 1.93/32.576 English (American) MIME-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on Domino01.lido-tech/Lido-Tech(Release 5.0.11 |July 24, 2002) at 04-12-2003 07:46:12,|July 24, 2002) at 04-12-2003 07:46:13, Serialize complete at 04-12-2003 07:46:13 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Subject: Re: Anti aliased fonts in FBSD X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: bernard.el-hagin@lido-tech.net List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2003 06:43:26 -0000 X-List-Received-Date: Thu, 04 Dec 2003 06:43:26 -0000 owner-freebsd-questions@freebsd.org wrote: >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 = capable of >> >> using them). Where exactly is this governed? How do I tell = applications >> >> 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 started. >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 also >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 with >the -DWITHOUT_XFT flag." > >So, do you have gVim built with gtk+-2 support, and have you done what >section 5.7.3.2 tells you for KDE/Qt apps (i.e. set QT_XFT to true)? I don't use KDE nor Gnome, but as I understand it any application which 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: 1. find out before building an application whether it will be built with support for either of those, 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). Thanks. Cheers, Bernard