ID: 42218
User updated by: fernando at barnatech dot com
Reported By: fernando at barnatech dot com
-Status: Feedback
+Status: Open
Bug Type: GD related
Operating System: Suse 10.2
PHP Version: 5.2.4RC1
Assigned To: pajoye
New Comment:
I'll ask to the sysadmin team for a recompilation without japanese
support and then for a test repetition. It can last for days, I think.
I'll tell you the progress, if there's some.
Previous Comments:
------------------------------------------------------------------------
[2007-08-09 07:47:24] [EMAIL PROTECTED]
About the install, on windows you don't have to install anything. You
can run php directly from the uncompressed directory, using the console
(cmd).
"By the way, may he bug disappear if PHP-GD is recompiled without
japanese support? The "any2eucjp()" in the error suggests it."
Yes, if you don't need japanese, disable it. I suspect a conflict
between the encoding.
------------------------------------------------------------------------
[2007-08-09 07:42:48] fernando at barnatech dot com
The code encoding is UTF-8 as I told. We carefully use UTF-8 for code
in the IDE, for data in the DBMS and for output in the webserver.
I think a test is not so easy to perform in my job environment. Usually
I have no direct access to installation privileges, further than limited
ones in the development servers. No access to clients administration, no
PHP installation, recompilation or direct reconfiguration without an
administrative permission, etc. I promise you it's not so easy.
Working with PHP 5.2.0 right now. The bug is there too, of course.
By the way, may he bug disappear if PHP-GD is recompiled without
japanese support? The "any2eucjp()" in the error suggests it.
------------------------------------------------------------------------
[2007-08-08 13:36:21] [EMAIL PROTECTED]
"I have no spare machines right now (resources fly here)."
Fetch a snapshot (windows for example), uncompress it and execute your
script using it. That's all I need :)
"I think I don't understand exactly what are you asking about
encoding.
For me, encoding is the charset used with data, or code, or HTML
output.
But it seems it's not what you're asking."
Which enconding do you use in your script files, iso-xxxx, UTF-8, etc.
Your editor should be able to tell you that. That determines what you
actually pass to the imagettf function (UTF-8 is the safest way).
------------------------------------------------------------------------
[2007-08-08 08:02:32] fernando at barnatech dot com
Strange, as I pasted directly that phpinfo() output. I had installed
the 5.2.4RC1 version on a dev webserver over a previously PHP version
test, but I'm afraid I can't do it again. It was a development
environment I set up when I found this bug in our stable dev version
5.2.0, just to test if it had been corrected in 5.2.4RC1, as a prior
step before reporting it here. But since yesterday that server doesn't
exist anymore, and I have no spare machines right now (resources fly
here).
I think I don't understand exactly what are you asking about encoding.
For me, encoding is the charset used with data, or code, or HTML output.
But it seems it's not what you're asking. I don't manage font charsets,
if it helps.
------------------------------------------------------------------------
[2007-08-06 17:15:14] [EMAIL PROTECTED]
Ok, I revert the process, easier than asking you again to comment
there...
For the record, when the status says "bogus", it means it is not a bug.
It can be hundred of reasons. I don't like this wording either but I'm
not alone to decide here. But that's no reason to begin a rant here and
now. I'm here to help you to fix a problem not to read rants.
"Well, more calmed now."
Good, you'll get more chance to get me reading your report if you are
calm.
So, about this bug. Which encoding do you use in your script?
Can you try with a true 5.2.4RC1 (what I see in your phpinfo details is
not from 5.2.4RC1, you should read "2.0.34...").
------------------------------------------------------------------------
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/42218
--
Edit this bug report at http://bugs.php.net/?id=42218&edit=1
