ID:               41666
 Updated by:       [EMAIL PROTECTED]
 Reported By:      cyberline at techno4ever dot net
-Status:           Open
+Status:           Bogus
 Bug Type:         GD related
 Operating System: Debian 3.1
 PHP Version:      5.2.3
 Assigned To:      pajoye
 New Comment:

"When it's a Freetype problem, i don't understand why the text looks so
since updating PHP to 5.2.3."

As I said, the text problem itself is due to the blending mode and
whether or not your save the alpha channel.

If the text is drawn on a fully (or partially) transparent area, the
antiliasing will be done using the alpha channel and not using blending.
If later on you save the image without alpha, the result is likely to be
ugly and the antialiasing effect will look wrong.

But if you disable the alphablending before the copy of the resized
logo, it will work well (using 5.2.3):

http://pierre.libgd.org/bugs/bug41666_523_out.png

It may also come from the hinting mode used in freetype, or its
options/settings. They have been changed between sarge and etch as far
as I remember. But that's not something I can see from phpinfo(). And it
is not something I can fix in GD.

"The working example at cyberline.ath.cx is Freetype 2.1.7 on Debian 4
with PHP 5.2.1"

Using debian packages for php, php-gd and freetype?

If yes, I _strongly_ suggest to stop using them for php and php-gd.
They use the extern GD library and an outdated version, no update has
been done since years and almost all security issues fixed in gd-2.0.34
or php's gd are still present.

Until I figured out a way to get it fixed (I'm working with one of the
php debian maintainers and the security team), I can' t support it or
even help someone using it.




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

[2007-06-12 13:15:14] cyberline at techno4ever dot net

http://www.host4ever.de/info.php

Freetype 2.1.7 on Debian 3.1

When it's a Freetype problem, i don't understand why the text looks so
since updating PHP to 5.2.3.

The working example at cyberline.ath.cx is Freetype 2.1.7 on Debian 4
with PHP 5.2.1

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

[2007-06-12 13:05:39] [EMAIL PROTECTED]

"I don't mean the transparent background!
My problem is the text."

As long as you have no alpha channel, there is no alpha either involved
in the text.

The text itself works pretty well here. Your problem looks more like a
hinting problem which depends on the freetype version, settings or
options. Can you show me a phpinfo and tell me which freetype version
you use and on which system.



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

[2007-06-12 12:54:03] cyberline at techno4ever dot net

I don't mean the transparent background!

My problem is the text.

Compare:

http://cyberline.ath.cx/phpbug/nok.php (PHP 5.2.1)
with
http://web1.server02.quadrat4.de/phpbug/nok.php (PHP 5.2.3)

Both same Configure.

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

[2007-06-12 12:05:03] [EMAIL PROTECTED]

"So it is not a bug that in 5.2.1 the alpha was enabled by default "

I don't have a 5.2.1 to test. The alpha channel is now preserved (the
background, the white area around the logo). nok.php is black because
you don't save the alpha channel.

I think this bug is not a bug. I close (not a bug > bogus) it now.
Please reopen it if you consider that it is not working correctly in
5.2.3 or using snapshot.

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

[2007-06-12 11:54:58] cyberline at techno4ever dot net

Now the 5.2.1 working Sample (nok.php) looks fine with imagesavealpha,
but take a look at the ok.php with

imagealphablending($image, 0);

So it is not a bug that in 5.2.1 the alpha was enabled by default ?

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

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/41666

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

Reply via email to