Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 0.7.0

Bug #17619 Warning: imagettfbbox() [function.imagettfbbox]: Could not read font ...
Submitted: 2010-07-21 22:30 UTC
From: hm2k Assigned: doconnor
Status: Closed Package: Image_Text (version SVN)
PHP Version: 5.3.2 OS:
Roadmaps: (Not assigned)    

 [2010-07-21 22:30 UTC] hm2k (James Wade)
Description: ------------ I'm trying out the supplied example.php (from SVN) and I'm getting this error: Warning: imagettfbbox() [function.imagettfbbox]: Could not read font in /usr/share/pear/Image/Text.php on line 832 Warning: imagettfbbox() [function.imagettfbbox]: Could not read font in /usr/share/pear/Image/Text.php on line 794 It's repeated many times, which seems to be because of bad error checking to ensure the font file is readable at the start. Although I understand that the error is because it can't read the font, but if this is the case, why is the "Fontfile not found or not readable." not being displayed in this case? Test script: --------------- example.php from the svn Expected result: ---------------- Display the example image(s). Actual result: -------------- Too much to display here...


 [2010-07-21 22:34 UTC] hm2k (James Wade)
I also found that if I comment out the font_file line in the options I get the following error: "Fontfile not found or not readable." Is a font a requirement? Can't it fall back on the default system font?
 [2010-07-22 16:38 UTC] hm2k (James Wade)
This error is caused by a corrupt or invalid font file. I reported the incorrectly described error to php: I believe what this script should do is test the font file to ensure it is valid before it attempts to run. I will include a patch.
 [2010-07-22 16:38 UTC] hm2k (James Wade)
 [2011-12-09 21:51 UTC] doconnor (Daniel O'Connor)
Marking package as unmaintained
 [2011-12-09 22:23 UTC] doconnor (Daniel O'Connor)
-Status: Open +Status: Closed -Assigned To: +Assigned To: doconnor
This bug has been fixed in SVN. If this was a documentation problem, the fix will appear on by the end of next Sunday (CET). If this was a problem with the website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.