From owner-freebsd-ports@FreeBSD.ORG Tue Sep 30 01:19:33 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E15BA16A4B3; Tue, 30 Sep 2003 01:19:33 -0700 (PDT) Received: from la-mail2.digilink.net (la2.digilink.net [205.147.0.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8E6644020; Tue, 30 Sep 2003 01:19:27 -0700 (PDT) (envelope-from metrol@metrol.net) Received: from metrol@metrol.net (mail.testequity.net [205.147.16.57]) by la-mail2.digilink.net (8.12.10/8.12.9) with ESMTP id h8U8JQpV009213 for ; Tue, 30 Sep 2003 01:19:27 -0700 (PDT) From: Michael Collette To: marcus@FreeBSD.org Date: Tue, 30 Sep 2003 01:15:05 -0700 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200309300115.05714.metrol@metrol.net> cc: FreeBSD Mailing Lists Subject: About that Freetype2 update X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Sep 2003 08:19:34 -0000 Marcus, The Freetype2 port itself worked quite nicely. Upgraded properly, no compile problems. I had been looking forward to seeing this get updated due to some visual problems with Scribus. Long story short, I uninstalled the new version and added the old one back in via a package. All of my TrueType fonts here got real jaggedy. They were readable, but the quality was seriously degraded. I run with a KDE desktop and no anti-aliasing, as this is a laptop. AA on an LCD screen just looks fuzzy. I should note that with AA turned on, the new Freetype2 does just fine. The not so subtle difference is when there isn't any AA help. I should also note that this was certainly no fix for Scribus. With the updated version of Freetype2 I wasn't able to even see any True Type fonts at all. Without doing any real investigative work, I'm leaning to one of three explanations here... 1. Something is goofy in this new version of Freetype2 2. Freetype2 reall wanted that byte code interpreter after all 3. I need to recompile the applications that depend on Freetype2 No major crisis here, as the old version seems to still be doing just fine. Thought I'd pass along what all I saw with this new one just the same. Later on, -- "In theory, there is no difference between theory and practice. In practice, there is." - Yogi Berra