Re: Re: com php-src: Remove T1Lib support (see #69698): NEWS UPGRADING ext/gd/config.m4 ext/gd/config.w32 ext/gd/gd.c ext/gd/php_gd.h
| From: | Pierre Joye | Date: | Fri, 29 May 2015 15:09:46 +0000 |
| Subject: | Re: Re: com php-src: Remove T1Lib support (see #69698): NEWS UPGRADING ext/gd/config.m4 ext/gd/config.w32 ext/gd/gd.c ext/gd/php_gd.h | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-86449@lists.php.net to get a copy of this message | ||
Agreed. Kalle asked me on irc. I replied I agreed to kill it, but it did
not mean we should do it without a rfc.
While it really not used (or i did not find any code,
https://github.com/search?utf8=%E2%9C%93&q=imagepstext),
we could provide
them using freetype, which works just fine now with t1 fonts. If desired :)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Le 29/05/2015 09:18, Kalle Sommer Nielsen a écrit :
> Commit: 7dcfdbbee431c93c52605e1df323d18e0c6088e9 Author:
> Kalle Sommer Nielsen <kalle@php.net> Fri, 29 May 2015
> 09:18:36 +0200 Parents: 0e079f9358be65c4cae5dd938b4924abec0564ac
> Branches: master
>
> Link:
> 2/B3'�ÔŽß�·±Ûó
> http://git.php.net/?p=php-src.git;a=commitdiff;h=7dcfdbbee431c93c52605
e1df323d18e0c6088e9
>
> Log: Remove T1Lib support (see #69698)
Isn't a bit strange to drop this feature without discussion / RFC ?
Especially when we keep mcrypt which also rely on a dead upstream, and
which is much more problematic for security (crypto)
Remi.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlVoSEkACgkQYUppBSnxahhlfQCfZIDVw/9oak4q5MrOGwcExPj1
Ce0AoOSq3FCv0C4s43fbD6b3Q+BqWlMU
=m2Gu
-----END PGP SIGNATURE-----
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php