rasmus                                   Mon, 12 Mar 2012 06:11:58 +0000

Revision: http://svn.php.net/viewvc?view=revision&revision=324124

Log:
This change was badly worded and filed in the wrong section.
This isn't an ini change at all.

Changed paths:
    U   php/php-src/branches/PHP_5_4/UPGRADING

Modified: php/php-src/branches/PHP_5_4/UPGRADING
===================================================================
--- php/php-src/branches/PHP_5_4/UPGRADING      2012-03-12 05:58:15 UTC (rev 
324123)
+++ php/php-src/branches/PHP_5_4/UPGRADING      2012-03-12 06:11:58 UTC (rev 
324124)
@@ -36,15 +36,6 @@
 1. Changes to INI directives
 =============================

-- The default character set is now UTF-8 when the default_charset
-  php.ini directive is not explicitly set. This applies to functions
-  such as htmlentities() and htmlspecialchars(). If you were relying
-  on the previous default of ISO-8859-1 you will need to add:
-
-    default_charset = iso-8859-1
-
-  to your php.ini to preserve pre-PHP 5.4 behavior.
-
 - PHP 5.4 now checks at compile time if /dev/urandom or /dev/arandom
   are present.  If either is available, session.entropy_file now
   defaults to that file and session.entropy_length defaults to 32.
@@ -200,6 +191,13 @@

 - call_user_func_array() no longer allows call-time pass by reference.

+- the default character set for htmlspecialchars() and htmlentities() is
+  now UTF-8. In previous versions it was ISO-8859-1. Note that changing
+  your output charset via the php.ini default_charset directive does not
+  affect htmlspecialchars/htmlentities unless you are passing "" (an
+  empty string) as the encoding parameter to your htmlspecialchars/htmlentities
+  calls.
+
 - htmlentities() and htmlspecialchars() are stricter in the code units they
   accept for the asian encodings. For Big5-HKSCS, the octets 0x80 and 0xFF are
   rejected.  For GB2312/EUC-CN, the octets 0x8E, 0x8F, 0xA0 and 0xFF are

-- 
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to