Re: Default input encoding for htmlspecialchars/htmlentities

On 23/08/12 17:15, Rasmus Lerdorf wrote:

On 08/23/2012 09:09 AM, Andrew Faulds wrote:

Personally, I think you should have just two encodings: page_encoding and internal_encoding. The former is for form input and page output (could be latin-1, for instance), and internal_encoding is the internal representation (default to utf-8 - you can deal with all of, say, latin-1, as well as unicode entities). Input and output, on the web at least, are almost always going to match.

No, we need 3. The internal/script encoding doesn't have to be the same as the input encoding. It isn't common in the Western world, but elsewhere people do write their scripts in their local encoding which may very well be different from their input and/or output encodings. -Rasmus Oh, you mean script encoding, form input/page output encoding and internal representation?

Because I don't see a need for differing default input (i.e. file/form input) and default output (i.e. page/file output) encodings. -- Andrew Faulds http://ajf.me/