Romain Gilliotte escribió:
Quote:
mijn naam escribió:
Quote:
>Can someone please explain to me why/when one would use
>htmlspecialchars instead of htmlentities?
>>
>I know: if you only want to get certain characters translated. This
>is not the answer I'm looking for, I would like to know *why* you
>would want that, as opposed to a full translation.
>
htmlspecialchars allows you, per example to display HTML Code (not have
it interpreted by the browser).
Can be useful if you are coding a BBS and you want the BBCode tags to work, so that users can post examples.
>
htmlentities will replace everything it can.
Can be useful if your want to store accentued letters in a database that
does not support it (does that exists?), or to be really sure that all
of your users are going to see accentued letters, even without setting
correctly the charset you are using.
>
Well that's what I believe at least.
I may be wrong, and I'm sure their are better uses of htmlentities that
displaying correctly content with a badly setted charset
I found this on php.net:
richard at aggmedia dot net
13-Mar-2008 04:32
From SR:
Quote:
There's no sane reason to use htmlentities() instead
of htmlspecialchars(). As long as you specify the charset
of a page with a Content-Type meta in the head of a
page (which you should ALWAYS do in the first place),
escaping all characters is completely pointless and will
only grow the size of your page. Only the special HTML
characters (<, >, &, etc.) need to be escaped, which is
exactly what htmlspecialchars() does
This is inaccurate and unhelpful.
There are many cases where you would want to convert a UTF-8 (or other)
encoded string into appropriate HTML entity representations, as well as
being just good practice to use more compatable entities instead of
embedded character encodings.
One such example is when using JavaScript for string manipulation, which
doesn't support character sets and thus does not respect the UTF-8 BOM.
By converting to full entities, JavaScript works with the entity text
instead of byte codes.
So long as the developer understands what is happening with encoding and
how character sets work, they should make their own call on which
function they need to use.
