Sun Oct 10 23:45:55 2004tony [...] develop-help.com - Ticket created
From:
Tony Cook <tony [...] develop-help.com>
Date:
Mon, 11 Oct 2004 13:46:00 +1000
To:
bug-Imager [...] rt.cpan.org
Subject:
i_ft2_glyph_name implementation tries to store a unicode code point in an unsiged char
This needs a test written and then to be fixed.
Sun Oct 10 23:55:47 2004TONYC [...] cpan.org - Requestor tony@develop-help.com deleted
Sun Oct 10 23:55:47 2004TONYC [...] cpan.org - Requestor TONYC added
Wed Oct 13 08:06:43 2004TONYC [...] cpan.org - Correspondence added
In the original bug report I was referring to the XS implementation - it
looks like the C implementation has the same problem - accepting an
unsigned char when it should really accept an unsigned long (for unicode).
Wed Oct 13 10:35:41 2004TONYC [...] cpan.org - Correspondence added
Fixed for freetype 2 after some messing around (FT_Has_PS_Glyph_Names()
seems to always return false for truetype fonts <sigh>)
Still need to check the FT1.x code and the T1lib code (though it's more
a problem for the FT1.x code - T1 only allows 256 chars anyway)
Mon Oct 18 11:00:52 2004TONYC [...] cpan.org - Correspondence added
The FT1.x and T1 code had similar problems. Both have been fixed.
Tests have been added.
Fixed in CVS for 0.43_02
Mon Oct 18 11:00:53 2004TONYC [...] cpan.org - Given to TONYC
Mon Oct 18 11:00:53 2004TONYC [...] cpan.org - Status changed from 'new' to 'resolved'
RT for rt.cpan.org