From owner-freebsd-gnome Fri May 31 13:48:46 2002 Delivered-To: freebsd-gnome@freebsd.org Received: from gyros.marcuscom.com (dhcp-64-102-60-60.cisco.com [64.102.60.60]) by hub.freebsd.org (Postfix) with ESMTP id 630A137B406 for ; Fri, 31 May 2002 13:48:42 -0700 (PDT) Received: from gyros.marcuscom.com (localhost [127.0.0.1]) by gyros.marcuscom.com (8.12.3/8.12.3) with ESMTP id g4VKm6xB053509; Fri, 31 May 2002 16:48:06 -0400 (EDT) (envelope-from marcus@marcuscom.com) Received: (from marcus@localhost) by gyros.marcuscom.com (8.12.3/8.12.3/Submit) id g4VKm6d6053508; Fri, 31 May 2002 16:48:06 -0400 (EDT) X-Authentication-Warning: gyros.marcuscom.com: marcus set sender to marcus@marcuscom.com using -f Subject: Re: pango broken with latest freetype? From: Joe Marcus Clarke To: Franz Klammer Cc: gnome@FreeBSD.ORG In-Reply-To: <1022877214.45242.36.camel@ncc-1701.webonaut.com> References: <1022833144.771.31.camel@ncc-1701.webonaut.com> <1022862065.50859.2.camel@gyros.marcuscom.com> <1022869058.56451.13.camel@ncc-1701.webonaut.com> <1022873704.70647.44.camel@gyros.marcuscom.com> <1022877214.45242.36.camel@ncc-1701.webonaut.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 31 May 2002 16:48:05 -0400 Message-Id: <1022878085.70647.68.camel@gyros.marcuscom.com> Mime-Version: 1.0 Sender: owner-freebsd-gnome@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 2002-05-31 at 16:33, Franz Klammer wrote: > Am Fr, 2002-05-31 um 21.35 schrieb Joe Marcus Clarke: > > On Fri, 2002-05-31 at 14:17, Franz Klammer wrote: > > > Am Fr, 2002-05-31 um 18.21 schrieb Joe Marcus Clarke: > > > > On Fri, 2002-05-31 at 04:19, Franz Klammer wrote: > > > > > Hi! > > > > > > > > > > As Joe tells me that my "I'm seeing some reports that say your > > > > > anti-alias/Xinerama issue is a bug in freetype2." i did > > > > > yesterday an update of freetype2 from the second last to > > > > > the latest version. > > > > > everything seems to work fine. only gdm2 displays no text > > > > > exept in the username/password input field. > > > > > > > > Well, I don't know what to tell you. I just downgraded to > > > > freetype2-2.0.9, and Nautilus displays glyphs again. I know 2.1.0 has a > > > > lot of changes for the conversion to the new freetype API. Perhaps it's > > > > incompatible with GNOME currently. > > > > > > > > I know the latest release of GARNOME shipped with 2.0.9 even though > > > > 2.1.0 was available. Maxim, are things working okay for you with the > > > > new freetype2? > > > > > > > > > > doesn't matter! i can work with my pc as ususal. that's important. > > > if it is necessary i will downgrade too. > > > > Here are the patches to freetype-2.1.0 to fix the problem with glyph > > rending in nautilus. It may also fix your problems with pango. Just > > place the files in print/freetype2/files, and build. > > > > short: how i can see resp. say - yes it fixes my problems but it only > revert my system back to the state before FT2-update. > > longer: > - gdm2 now displays fonts again. > - nautilus2 and some other gnome-programs still have the > same problem with Xinerama. exact like the screenshot i sent you. > - i also tried to build (not install) pango-1.0.1 but it fails with the > same errors as i sent you before.actually i've installed pango-1.0.2. > > the interesting thing is that, not like you've written, nautilus > displayes fonts after FT-update. before your patches, as i've seen, > only gdm2(graphical) and the spash-screen doesn't displays text. This is because the problem was with librsvg's use of the FT library. In nautilus2, librsvg defers to pango for freetype rendering. As long as pango works, then so will Nautilus. > > i hope i was able to help you. please tell me if you need more. Okay, this is good info. The FreeBSD GNOME community has a choice to make then. Do we apply these patches to FT 2.1.0, and mess up Xinerama support, but allow older GNOME 1.4.x users to be happy, or go without the patches, and force GNOME 1.4.x users to either stay on FT 2.0.9, or deal with the rending problems in librsvg? Or, do we offer this as a compile-time option to users? Or, do we revert back to 2.0.9? I'm hoping the freetype developers will be able to shed some more light on this problem. Perhaps this is something they can fix. If we decide to stay with FT 2.1.0, I will do the update of GTK+-2.0 and friends so that they will build with the new FT. Joe > > franz > > -- > WEBONAUT.com > http://webonaut.com > mailto:klammer@webonaut.com > Tel.: +43-664-3434708 > > -- PGP Key : http://www.marcuscom.com/pgp.asc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-gnome" in the body of the message