Opened 23 years ago

Closed 18 years ago

#2 closed defect (wontfix)

Non-antialiasing with FreeType 2 corrupts images.

Reported by: sdlime Owned by: sdlime
Priority: normal Milestone:
Component: MapServer C Library Version: 3.5
Severity: normal Keywords:
Cc:

Description

Not using antialiasing with TrueType fonts and FreeType 2 causes corruption of 
GD image output. Most likely a GD/FreeType problem, but I told John that I 
would patch both versions of the GD/FreeType code to fix font rendering with 
non-antialiased fonts. With FreeType 1 there is an error in his code that 
always requests grayscale pixmaps even with no antialiasing. It should request 
a bitmap instead. Fix is to add a key to his caching code and this was already 
written for versions 3.4 and earlier. I suspect the same problem exists with 
FreeType 2 since it uses the same caching code, however since not setting the 
antialias flag corrupts the image I can't tell. Will have to fix that first.

Workaround is to use antialiasing with TrueType fonts.

Change History (4)

comment:1 by sdlime, 23 years ago

Status: newassigned

comment:2 by sdlime, 23 years ago

Resolution: fixed
Status: assignedclosed

comment:3 by sdlime, 23 years ago

Resolution: fixed
Status: closedreopened

comment:4 by sdlime, 18 years ago

Resolution: wontfix
Status: reopenedclosed
We've come a long way since this bug was written. Closing...

Steve
Note: See TracTickets for help on using tickets.