|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2002-06-22 12:45 UTC] mfischer@php.net
[2002-06-24 03:54 UTC] mathias dot grub at web dot de
|
|||||||||||||||||||||||||||
Copyright © 2001-2025 The PHP GroupAll rights reserved. |
Last updated: Tue Dec 16 21:00:02 2025 UTC |
When running PHP with GD > 2 and Freetype >= 2 all functions which use ttf fonts (different from the built-in fonts (1-5)) don't draw the requested text string on the image, eg: imageLoadFont($pathtofont)or die('damn, cannot loadit'); results always in the 'or die()' part. In any case. Independent on if you use doc-relative path, root-relative path or absolute path (including drive letter/ IP). The windows binary of PHP 4.06 comes with GD 1.64. And phpinfo() says for 'FreeType Linkage' TrueType Library. If this is so, the above and following problems don't appear and solved. But the PHP 4.10, 4.11, 4.12 Windows Distributions come with GD 2.0 or higher and obviously with freetype V.1, because the function imageFTtext() creates an error: Freetype 2 is required. OK, lets install PHP 4.21 to get Freetype 2 support. Well done, the error message when using imageTTFtext() or imageFTtext is gone, but the wanted string is left blank. Beside to the function above imageloadfont()or die(); which always ends in the or die part. I guess the trio PHP 4.2/GD2/Freetype2 is not able to write text with ttf fonts onto an image. Seems to be an (evil, bad) bug. Am I right?