Resolves https://rt.cpan.org/Ticket/Display.html?id=7581
- built 0.43_01 for testing
+0.43_02 Mon 26 Oct 2004
+
+- the changes to scale() had some problems with integer vs floating point
+ calculations (only caught in tests under perl 5.8.5 <sigh>)
+- the FT2 glyph_names() method didn't do correct error handling
+ when the string parameter wasn't supplied
+- i_ft2_glyph_name() accepted only an unsigned char as the
+ character code to get the name for, which meant it
+ didn't work for unicode characters \x{100} or above
+- the XS for i_ft2_glyph_name() had a similar problem
+- added NameTest.ttf to be used in checking unicode glyph
+ names
+- added reliable_only optional parameter to the glyph_names()
+ method so you can ignore theresult of FT_Has_PS_Glyph_Names()
+- handle errors given by i_ft2_glyph_name() a bit more
+ correctly
+- the FT1 glyph_names() method didn't do correct error handling
+ when the string parameter wasn't supplied
+- some memory allocated when creating a callback IO object (io_new_cb)
+ wasn't being released (detected with valgrind)
+- the testtools.pl match[nx]() functions escapes the test string on
+ test failure a bit better
+- the XS code for i_tt_glyph_name() used unsigned char to store a
+ unicode character when it should have used unsigned long.
+- the XS code for i_t1_glyph_name() used unsigned char to store a
+ unicode character when it should have used unsigned long.
+- resolves https://rt.cpan.org/Ticket/Display.html?id=7949
+- the type 1 glyph_names() method didn't do correct error handling
+ when the string parameter wasn't supplied
+- renamed io.h to imio.h to prevent problems building under cygwin.
+ resolve https://rt.cpan.org/Ticket/Display.html?id=7948
+- i_writegif_low() wasn't setting the returned global palette, which
+ meant a rubbish palette was returned to the user (detected with valgrind)
+- built 0.43_02 for testing
+
+0.43_03
+
+- change the "double-include" protection macro that imio.h uses.
+- updated download locations for the various libraries that Imager
+ depends on. Added some advice for cygwin.
+- more information on gif library versions in README and Makefile.PL
+- creating an image where the size of the allocated image buffer would
+ overflow an integer would cause too small a buffer to be allocated.
+ This could potentially be a security hole.
+ partly resolves https://rt.cpan.org/Ticket/Display.html?id=8213
+- set i_format to jpeg for jpeg files and test for it
+- set i_format to png when reading png files and test for it
+- i_yres was being set to the xres when reading a png file
+- added many bad BMP files to test various code paths in bmp.c, and
+ made many minor fixes to bmp.c to make them work:
+ - it was possible for various types of read failures to SEGV, both
+ as NULL pointer dereferences and buffer overflows
+ - some errors, like palettes being too large for the number of bits
+ per pixel, were not being caught
+ - failing to read all of a packed data structure would not cause
+ a read failure
+ - invalid compression types were not always caught
+ - error messages are more consistent (still not always great messages,
+ but one step at a time)
+- added bmp_compression_name, bmp_used_colors, bmp_filesize, bmp_bit_count
+ tags on reading a BMP file
+- added tools/imager to the distribution. This is still very
+ experimental and untested. Patches welcome, if you write tests to go
+ with them.
+- the BMP reader now validates the bfOffBits value from the BMP header
+ and skips to that offset before reading image data. Previously this
+ value was read but otherwise ignored.
+- added --palette action to tools/imager
+- i_img_pal_new() now releases the image object memory if creation
+ fails.
+
=================================================================
For latest versions check the Imager-devel pages:
- http://imager.perl.org/~addi/perl/Imager/
+ http://imager.perl.org/
=================================================================