On Sat, Mar 14, 2009 at 12:18 AM, Lester Caine wrote:
> This probably one of the reasons some of us think that getting a stable PHP6
> based on unicode out of the door would probably be a lot more use to people
> than PHP5.3 ;)
+1
I cannot wait for full unicode. mbstring, iconv, all this wacky
Heddon's Gate Hotel wrote:
Thanks Jan, it's much clearer now. My knowledge about character
encodings has multiplied 100-fold in the last 24 hours' research.
Would it be a good idea for the PHP Manual to address some of these
issues, by explaining good practice in encoding arbitrary user input
Thanks Jan, it's much clearer now. My knowledge about character
encodings has multiplied 100-fold in the last 24 hours' research.
Would it be a good idea for the PHP Manual to address some of these
issues, by explaining good practice in encoding arbitrary user input in
forms (for example), fo
2009/3/13 Heddon's Gate Hotel :
> The string function htmlentities seems to have very incomplete coverage of
> the HTML entities listed in the HTML 4 spec. For example, it does not know
> about rsquo, lsquo, rdquo, ldquo, etc. This is confirmed by looking at the
> output of get_html_translation_t
The string function htmlentities seems to have very incomplete coverage
of the HTML entities listed in the HTML 4 spec. For example, it does
not know about rsquo, lsquo, rdquo, ldquo, etc. This is confirmed by
looking at the output of get_html_translation_table, which does not list
these enti
5 matches
Mail list logo
