We've kept the GD renderer in 6.0 for some marginal use cases, but the preferred way is to switch to AGG rendering (which is compiled in by default): you can use the builtin png8 imagetype (mimetype: image/png; mode=8bit) which does a quantization step if you need a 256 color paletted image.
The easy solution is to remove all your outputformat blocks from your mapfile, and call your server with FORMAT=image/png or image/png; mode=8bit , and setting your map imagetype to png or png8. As for this GD rendering bug, the easy first step is be to open a bug-report. The harder second step is to get someone motivated to look into it if you cannot provide a patch. regards, thomas On Thu, Jul 7, 2011 at 20:07, Brad Posthumus <posthum...@agr.gc.ca> wrote: > I've narrowed it down further to the OUTPUTFORMAT section of the mapfile, > which currently is: > > OUTPUTFORMAT > NAME png > DRIVER "GD/PNG" > MIMETYPE "image/png" > IMAGEMODE PC256 > FORMATOPTION "INTERLACE=OFF" > EXTENSION png > TRANSPARENT ON > END > > It appears to be a problem with having a combination of GD/PNG, PC256, and > transparency. Turning transparency off renders a clean image, changing PC256 > to RGBA renders a clean image, changing PNG to GIF (at all locations) > renders a clean image.... > > This setup was working in 5.4 and 5.6 so I'll assume it's a bug I should > report for 6.0. > > -- > View this message in context: > http://osgeo-org.1803224.n2.nabble.com/Font-rendering-in-MapServer-6-0-tp6555935p6559374.html > Sent from the Mapserver - User mailing list archive at Nabble.com. > _______________________________________________ > mapserver-users mailing list > mapserver-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/mapserver-users > _______________________________________________ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users