At 16:24 17.10.2002, Colin Viebrock wrote:
We only show what we do this way. In other way we declare the> Why did you remove the charset info? > > I want my charset back since it enables correct handling of the output. > Everything these lines commented out by you do is telling the receiver > what charset he gets. That is compareable to http charset info which > will be generated by those modules also. This way you can enable > mbsting or iconv with any charset you like. > > This has nothing to do with the other thing you did in this patch: > changing behaviour of php_escape_html_entities(). I guess you did > not understand what you removed?No, I do understand what I did. Every browser I tested displayed the phpinfo() page correctly when the charset was not specified ... i.e., they guessed the right charset. If you explicitly specify a charset, then you need to encode the characters according to that character set. The problem is, that encodings such as é and Ä (which show up on the credits page), don't work under all charsets/encodings.
charset used in the TRANSPORT LAYER.
Please read w3c documentation:
http://www.w3.org/TR/html401/struct/global.html#adef-http-equiv
[...]
META and default information
The META element may be used to specify the default information for a document in the following instances:
[...]
· The document character encoding.
The following example specifies the character encoding for a document as being ISO-8859-5
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-5">
[...]
and also the referred document:
http://www.w3.org/TR/html401/charset.html#doc-char-set
[...]
For example, to specify that the character encoding of the current document is "EUC-JP", a document should include the following META declaration:
<META http-equiv="Content-Type" content="text/html; charset=EUC-JP">
The META declaration must only be used when the character encoding is organized such that ASCII-valued bytes stand for ASCII characters (at least until the META element is parsed). META declarations should appear as early as possible in the HEAD element.
For cases where neither the HTTP protocol nor the META element provides information about the character encoding of a document, HTML also provides the charset attribute on several elements. By combining these mechanisms, an author can greatly improve the chances that, when the user retrieves a resource, the user agent will recognize the character encoding.
To sum up, conforming user agents must observe the following priorities when determining a document's character encoding (from highest priority to lowest):
1. An HTTP "charset" parameter in a "Content-Type" field.
2. A META declaration with "http-equiv" set to "Content-Type" and a value set for "charset".
3. The charset attribute set on an element that designates an external resource.
[...]
I will test it again, with the charset declaration back in, but I'm relying on people with non-Western browsers and charsets for some feedback on how the choice of charset affects the rendering of the pages. - Colin
