#42218 [Bgs->Opn]: ImageTTFBBox & any2eucjp

From: Date: Mon, 06 Aug 2007 15:29:26 +0000
Subject: #42218 [Bgs->Opn]: ImageTTFBBox & any2eucjp
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-115801@lists.php.net to get a copy of this message
 ID:               42218
 User updated by:  fernando at barnatech dot com
 Reported By:      fernando at barnatech dot com
-Status:           Bogus
+Status:           Open
 Bug Type:         GD related
 Operating System: Suse 10.2
 PHP Version:      5.2.4RC1
 New Comment:

Well, more calmed now. I'll try to refine my report, as the original
bug is mistakenly closed (and comments there now allowed) due to bad
version reporting, and I can't post this anywhere but here.

I have verified this issue still happens in version 5.2.4RC1 with any
string containing the euro sign. I can't verify it happens with other
special signs, as the original bug reported, but the euro sign itself is
critical enough for business reports.

This is my own offending code. It's exactly the same code as the
original posted, but the special "offending" char diffier.


Code to reproduce:

list($x1,,$x2) = imagettfbbox(8, 0,
'/var/www/virtual/external.dev/framework/dompdf/lib/fonts/Arial.ttf',
'€');


Unexpected result:

Warning: imagettfbbox() [function.imagettfbbox]: any2eucjp(): invalid
code in input string in
/var/www/virtual/external.dev/framework/dompdf/include/gd_adapter.cls.php
on line 597


Code, data and encoding along all the application is UTF-8.

Details on GD used:
GD Support 	enabled
GD Version 	bundled (2.0.28 compatible)
FreeType Support 	enabled
FreeType Linkage 	with freetype
FreeType Version 	2.2.2
GIF Read Support 	enabled
GIF Create Support 	enabled
JPG Support 	enabled
PNG Support 	enabled
WBMP Support 	enabled
XPM Support 	enabled
XBM Support 	enabled
JIS-mapped Japanese Font Support 	enabled


Previous Comments:
------------------------------------------------------------------------

[2007-08-06 15:21:15] fernando at barnatech dot com

Sorry, regarding to bug #39543, I thought "closed" meant "closed". It's
a little nonsense to address me to a bug that is closed just for bad
version reporting, as I'm opening it for the most current version, and I
can't reopen the closed old one, nor post any comment there.

In fact, I simply cannot post any comment in bug #39543 (it was the
first thing I attempted, as you can imagine), because someone sealed
that bug just because the version was mistakenly reported as 5.1.2. But
the bug is in current version 5.2.4RC1, at least with the euro sign.

I'm very astonished to see that someone has used a bad version
reporting mistake to close these two bugs without the possibility to add
further comments or verifications to them. It gives the feeling that
people looks at these bug reporting thing with no other intention than
closing them without a real test.

Excuse me, but I can't understand this bug reporting dynamic. It seems
proved that bugs like this one are simply lost. And it's a bit offending
to see someone sending me to post a comment in a mistakenly closed bug
report where I can't post anything.

"By the way, there are no font bugs solved since PHP 5.0.4."
My comment was based in the changelog. As we're told, please check the
changelog. I've done it.

------------------------------------------------------------------------

[2007-08-06 11:55:21] pajoye@php.net

Don't open two bugs for the same issue.

"By the way, there are no font bugs solved since PHP 5.0.4."

So wrong. if you have any issue with the ttf function, please report
them with:
- the font you use
- a script to reproduce it
- the encoding used in your script

Thanks.

But I close this bug as duplicated of #39543 (> bogus). Add your
comments to #39543.

------------------------------------------------------------------------

[2007-08-06 11:42:42] fernando at barnatech dot com

Description:
------------
I don't know why bug #39543 is closed, as it's still alive in
5.2.4RC1.

The original poster of the bug proved it with accented letters. In my
case the trouble comes from the euro sign (a very big trouble, IMHO).
Tipically related to non ascii encoding.

By the way, there are no font bugs solved since PHP 5.0.4.

Reproduce code:
---------------
<?php
$bounds = ImageTTFBBox(9,0,              
'/home/max/workspace/wwwdev/libraries/jpgraph/ttf/arial.ttf',
'áéíóú'
);
?>

or

<?php
$bounds = ImageTTFBBox(9,0,              
'/home/max/workspace/wwwdev/libraries/jpgraph/ttf/arial.ttf',
'€'
);
?>

Expected result:
----------------
no warning

Actual result:
--------------
Warning: imagettfbbox() [function.imagettfbbox]: any2eucjp(): invalid
code in input string in /home/max/workspace/wwwdev/web/test.php on
line
5


------------------------------------------------------------------------


-- 
Edit this bug report at http://bugs.php.net/?id=42218&edit=1


Thread (24 messages)

« previous php.bugs (#115801) next »