Re: svn: /php/php-src/trunk/ NEWS ext/standard/html.c ext/standard/tests/strings/bug44703.phpt
ext/standard/tests/strings/get_html_translation_table_basic1.phpt ext/standard/tests/strings/get_html_translation_table_basic2.phpt ext/standard/
| From: | Hannes Magnusson | Date: | Fri, 26 Mar 2010 13:54:10 +0000 |
| Subject: | Re: svn: /php/php-src/trunk/ NEWS ext/standard/html.c ext/standard/tests/strings/bug44703.phpt ext/standard/tests/strings/get_html_translation_table_basic1.phpt ext/standard/tests/strings/get_html_translation_table_basic2.phpt ext/standard/ |
||
| Groups: | php.cvs php.internals | ||
| Request: | Send a blank email to internals+get-47643@lists.php.net to get a copy of this message | ||
2010/3/26 Johannes Schlüter <johannes@php.net>:
> On Tue, 2010-03-23 at 18:08 +0000, Rasmus Lerdorf wrote:
> With the environments using more and more Utf-8 (operating system
> environments, editor defaults, ...) the change is good but it is no
> small thing but will cause "trouble" for many users having iso-8859-1
> texts in their database and getting broken pages after the upgrade and
> we should advise users to mind their encodings!
It is clearly noted in the upgrade guide...
If you have a pre-existing app on the server then update your INI file.
For new apps, use the default..
As long as we list it in the upgrade guide, and potentionally in the
"Backwards compatibility breakages" listing..
Its an "simple and easy one-time-fix" to php.ini.
If it was about swapping parameter order to function, or completely
different return value or anything that a developer needs to really
scan his code for, then thats a different story - but a default ini
value?
-Hannes