htmlentities()
is not a guaranteed way to build legal XML.
Use htmlspecialchars()
instead of htmlentities()
if this is all you are worried about. If you have encoding mismatches between the representation of your data and the encoding of your XML document, htmlentities()
may serve to work around/cover them up (it will bloat your XML size in doing so). I believe it's better to get your encodings consistent and just use htmlspecialchars()
.
Also, be aware that if you pump the return value of htmlspecialchars()
inside XML attributes delimited with single quotes, you will need to pass the ENT_QUOTES
flag as well so that any single quotes in your source string are properly encoded as well. I suggest doing this anyway, as it makes your code immune to bugs resulting from someone using single quotes for XML attributes in the future.
Edit: To clarify:
htmlentities()
will convert a number of non-ANSI characters (I assume this is what you mean by UTF-8 data) to entities (which are represented with just ANSI characters). However, it cannot do so for any characters which do not have a corresponding entity, and so cannot guarantee that its return value consists only of ANSI characters. That's why I 'm suggesting to not use it.
If encoding is a possible issue, handle it explicitly (e.g. with iconv()
).
Edit 2: Improved answer taking into account Josh Davis's comment belowis .
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…