Date: Tue, 30 Sep 2003 20:02:45 -0400 From: parv <parv_fm@emailgroups.net> To: Franz Klammer <klammer@webonaut.com> Cc: FreeBSD Mailing Lists <freebsd-ports@FreeBSD.org> Subject: Re: About that Freetype2 update Message-ID: <20031001000245.GA360@moo.holy.cow> In-Reply-To: <1064934538.46705.13.camel@sisko.webonaut.com> References: <200309300115.05714.metrol@metrol.net> <1064910135.48606.6.camel@shumai.marcuscom.com> <1064934538.46705.13.camel@sisko.webonaut.com>
next in thread | previous in thread | raw e-mail | index | archive | help
in message <1064934538.46705.13.camel@sisko.webonaut.com>, wrote Franz Klammer thusly... > > i had the a problem with blur font display after upgrading to the > latest version. adding back bytecode solves it. > > here some screenshots with and without bytcode enabled: > > http://webonaut.com/temp/bytecode/ Interesting! I had only seen[0] the fuzzier version of an anti-aliased font (as seen in "*without_bytecode*" images), believing it to be the "feature" of anti aliasing. That, the fuzziness, was highly distracting, so i have been using plain olde UN-anti-aliased(?) fonts. Now i know better. Thanks everybody. [0] I saw fuzziness in fvwm 2.5.x, xterm, and Mozilla, all running w/ help of XFree86 4.2.0. I did not note the whether the version of freetype. - Parv --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031001000245.GA360>