#22092 [Opn->Fbk]: Strange warning and no functionality in imagettfbbox and imagettftext

ID: 22092 Updated by: iliaa@php.net Reported By: davidl@tocquigny.com -Status: Open +Status: Feedback Bug Type: GD related Operating System: Redhat 7.1 PHP Version: 4.3.0 New Comment: Please try using this CVS snapshot: http://snaps.php.net/php4-STABLE-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-STABLE-latest.zip Also, try specifying the full path to the font, by doing realpath() on the font path before passing it to imagettfbox(). Previous Comments: ------------------------------------------------------------------------ [2003-02-06 15:15:28] davidl@tocquigny.com Also, it won't accept spaces in the font file name, if I have no spaces (ie arial.ttf) it works, with spaces (ie "futura bold.ttf") generates: Could not find/open font in /xxx/xxx/xxx/test2.php on line 3 ------------------------------------------------------------------------ [2003-02-06 15:01:53] davidl@tocquigny.com okies, that fixed one problem and created another (although MUCH LESS MAJOR) the results now: 1 Warning: imagettfbbox() [function.imagettfbbox]: Could not find/open font in /xxx/xxx/xxx/xxx/test2.php on line 3 if I put an absolute path into the font location, it works, but relative paths do not. ------------------------------------------------------------------------ [2003-02-06 13:33:10] iliaa@php.net Try adding the --with-freetype-dir option to your configure. As is I cannot replicate the bug using the latest CVS (4.3.1-dev). ------------------------------------------------------------------------ [2003-02-06 13:18:56] davidl@tocquigny.com also tried adding --with-ttf to the 4.3.0 compile, still no love ------------------------------------------------------------------------ [2003-02-06 12:48:16] davidl@tocquigny.com just fyi, I put the /xxx/xxx/xxx in the file path to hide my directory structure, however the gibberish for a warning came completely from php :) ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/22092 -- Edit this bug report at http://bugs.php.net/?id=22092&edit=1