ID: 26635 User updated by: choinet at rocketmail dot com Reported By: choinet at rocketmail dot com -Status: Open +Status: Closed Bug Type: Feature/Change Request Operating System: Windows XP PHP Version: 4CVS-2003-12-28 New Comment:
Forget it, I'll submit a separate bug report, as it is unrelated to the original report. Previous Comments: ------------------------------------------------------------------------ [2004-01-01 20:11:30] choinet at rocketmail dot com Let us straighten out a few points: 1. My system is properly configured. It is a standard readme installation and does not use anything out of the ordinary. Unzip zipped php file, move php.ini and php4ts.dll, uncomment php_gd2.dll and set display_errors to 'On' in php.ini, restart server. The fact that I *can* use font paths without spaces to properly use the function shows that nothing has been misconfigured. 2. snipers says that there is no bug here and that I should simply pretend that there is no problem. The screenshot http://icandy.sourceforge.net/phperror.gif plainly shows the problem occuring when I specify a pathname with spaces in it. Have you developers tried using the function with one or more spaces in the pathname? Because, of course, it will work if there are none in the pathname, but I'm talking about the spaces here. 3. This situation is not 'bogus'. If you look at the comments under the php manual at http://www.php.net/manual/en/function.imagettftext.php you'll see mhellmund AT exozet DOT com's and dev at strategma dot bg's comments, that "ImageTTFText seems to have problems with fonts residing in a directory tree with spaces." 4. This issue is slightly different from the original report, where relative pathnames could not be used. At the initial report, I was still using spaces in the pathnames, which would have overridden any of the other problems, and what may have been 'fixed' in regards to relative pathnames may not have had to be fixed at all, for relative pathnames worked fine on Linux (because the pathnames had no spaces in them). I'd like a very clear answer as to whether or not the developers tried pathnames with spaces in them, and if this is a PHP or a GDlib issue. This is I have heard from phpbuilder.net that it could possibly be that spaces are used to denote multiple fonts in an argument, but I want to hear the explanation directly from you people. If it can't be fixed, fine, then I guess the people on default Windows configurations will simply have to make do and not be able to use these functions with fonts in space-embedded pathnames. But I do not want to hear that there is no bug here when clearly something is amiss, albeit in PHP or the external library. ------------------------------------------------------------------------ [2003-12-30 12:27:18] choinet at rocketmail dot com If I did install/configure something incorrectly, I shouldn't have been able to use the imagettfbbox() and imagettftext() functions in the first place... ------------------------------------------------------------------------ [2003-12-30 10:28:08] [EMAIL PROTECTED] Please don't reopen this, there is no bug here. There's something wrong with your system.. (most likely you're not installing the snapshot correctly) ------------------------------------------------------------------------ [2003-12-28 18:26:14] choinet at rocketmail dot com eh, that hyperlink should be without the comma ------------------------------------------------------------------------ [2003-12-28 18:25:22] choinet at rocketmail dot com What am I doing wrong, then? Here's a screenshot at http://icandy.sourceforge.net/phperror.gif, showing the script and font file in c:\htdocs and c:\htdocs\test directory, respectively, as well as the source code and the instance of the problem. The warning was generated on Windows XP and Apache2 using the latest STABLE CVS (I also checked 4.3.4, latest 5.x CVS, and 5.0.0 beta 3) ------------------------------------------------------------------------ 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/26635 -- Edit this bug report at http://bugs.php.net/?id=26635&edit=1
