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

 ID:                 43896
 Updated by:         cataphr...@php.net
 Reported by:        arnaud dot lb at gmail dot com
 Summary:            htmlspecialchars() returns empty string on invalid
                     unicode sequence
-Status:             To be documented
+Status:             Closed
 Type:               Bug
 Package:            Strings related
 Operating System:   *
 PHP Version:        5CVS-2008-07-15
-Assigned To:        
+Assigned To:        cataphract
 Block user comment: N

 New Comment:

Noted addition of ENT_IGNORE in the manual entries for htmlspecialchars
and htmlentities.


Previous Comments:
------------------------------------------------------------------------
[2010-10-11 03:15:46] cataphr...@php.net

Automatic comment from SVN on behalf of cataphract
Revision: http://svn.php.net/viewvc/?view=revision&revision=304297
Log: - Documented addition of ENT_IGNORE as per bug #43896
  (changed its status from TBD to Closed).

------------------------------------------------------------------------
[2008-11-26 04:33:22] lbarn...@php.net

It seems "Fixed in CVS and need to be documented" does not changes the
status if it is set to "Assigned" :/

------------------------------------------------------------------------
[2008-11-26 04:30:41] lbarn...@php.net

Added ENT_IGNORE as a compatibility flag to skip invalid multibyte
sequences instead of returning an empty string (as iconv's //IGNORE).
These functions will still never return an invalid or incomplete
multibyte sequence.

Example: htmlspecialchars("...", ENT_QUOTES | ENT_COMPAT, "utf-8");

------------------------------------------------------------------------
[2008-11-02 13:27:46] j...@php.net

Arnaud, fix it yourself.

------------------------------------------------------------------------
[2008-10-21 12:08:38] j...@php.net

Actually "The tool" to use for incoming data is the filter extension..

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


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/bug.php?id=43896


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

Reply via email to