Bug #11972 for Imager: text anti-aliasing against transparent images incorrect

Tue Mar 22 18:36:06 2005 TONYC [...] cpan.org - Ticket created

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

Tue Mar 22 18:36:42 2005 TONYC [...] cpan.org - Severity Important added

Wed Feb 07 03:53:41 2007 TONYC [...] cpan.org - Correspondence added

fixed for freetype 2.x in svn

Wed Feb 07 03:53:43 2007 TONYC [...] cpan.org - Status changed from 'new' to 'open'

Sat May 05 01:04:29 2007 TONYC [...] cpan.org - Correspondence added

fixed in svn for freetype 1.x and T1lib

Sun May 20 21:18:24 2007 TONYC [...] cpan.org - Correspondence added

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

Sun May 20 21:18:26 2007 TONYC [...] cpan.org - Status changed from 'open' to 'resolved'