This queue is for tickets about the Imager CPAN distribution.

Maintainer(s)' notes

Tickets for Imager are now on github at https://github.com/tonycoz/imager

Report information
The Basics
Id:
11972
Status:
resolved
Priority:
Low/Low
Queue:

People
Owner:
Nobody in particular
Requestors:
TONYC [...] cpan.org
Cc:
AdminCc:

BugTracker
Severity:
Important
Broken in:
(no value)
Fixed in:
(no value)



Subject: text anti-aliasing against transparent images incorrect
currently if a pixel has 50 percent coverage for example of blue (0,0,255) and the target pixel value is (0,0,0,0), then the result pixel will be (0,0,127,127), but it should be (0,0,255,127) for correct display. Also, this will blend with existing color, eg. if the target pixel were (255,0,0,0) then the result will be (127,0,127,127) rather than (0,0,255,127). This problem seems to be in at least the FT1.x driver, and is probably in the others. This may also be a problem for other anti-aliased output done by Imager
fixed for freetype 2.x in svn
fixed in svn for freetype 1.x and T1lib
On Tue Mar 22 18:36:06 2005, TONYC wrote:
Show quoted text
> currently if a pixel has 50 percent coverage for example of blue > (0,0,255) and the target pixel value is (0,0,0,0), then the result pixel > will be (0,0,127,127), but it should be (0,0,255,127) for correct display. > > Also, this will blend with existing color, eg. if the target pixel were > (255,0,0,0) then the result will be (127,0,127,127) rather than > (0,0,255,127). > > This problem seems to be in at least the FT1.x driver, and is probably > in the others. > > This may also be a problem for other anti-aliased output done by Imager
Fixed in 0.58


This service runs on Request Tracker, is sponsored by The Perl Foundation, and maintained by Best Practical Solutions.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.