[Bug 458592] Differences in rendering in the original and 1.0.4 version
bugzilla at redhat.com
bugzilla at redhat.com
Thu Aug 21 17:52:27 UTC 2008
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=458592
--- Comment #12 from Sylvain Beucler <beuc at beuc.net> 2008-08-21 13:52:26 EDT ---
> Sylvain, do you know when TT_CONFIG_OPTION_BYTECODE_INTERPRETER was activated:
> I mean which package version of freetype?
Probably since 2006:
freetype (2.2.1-2) unstable; urgency=low
* Enable full bytecode interpreter instead of just the
"non-patented portions".
* Use $(CURDIR) instead of $(PWD) to build with sudo. Closes: #367579.
-- Keith Packard <keithp at keithp.com> Wed, 17 May 2006 00:00:35 -0500
http://packages.debian.org/changelogs/pool/main/f/freetype/freetype_2.3.7-1/changelog
> Sylvain, are you able to reproduce the problem on debian
> or gentoo for other apps?
With SDL_ttf and freetype2-demos, yes. I think other apps usually turn
onanti-aliasing which works-around the issue.
Note that Gentoo disables it in binary packages, but enables it in recompiled
packages.
> I tried on Ubuntu-8.04 but didn't see it there FWIW.
I just Tried on gNewSense (Ubuntu) LiveCD and it shows for me.
Procedure:
- 'ftview 16 liberation-fonts-1.04/LiverationSans-Regular.ttf'
- Type 'a'
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the fonts-bugs
mailing list