Re: cvs: php4 /ext/standard info.c

At 22:03 04.08.2002, Ilia A. wrote:

On August 4, 2002 03:27 pm, you wrote: At 20:57 04.08.2002, Georg Richter wrote:

georg           Sun Aug  4 14:57:02 2002 EDT

Modified files:

    /php4/ext/standard  info.c

Log: added meta tag (w3c compliance) Thx to Ilia Alshanetsky (ilia@prohost.org)

That's not really correct because the charset can be changed by ini settings: output_handler = mb_output_handler mbstring.http_output=<charset> Besides: nowhere in HTML4.01 standard is said that you need "Content-Type" meta tag. Instead you should have to inform about charset in http message envelope. So i think the meta tag should be removed. marcus First here is the W3C document identifying the fact that charset is defined. http://www.w3.org/International/O-charset.html

I did not say there is no such tag - i said it is not required. The w3c says it is important to know the charset - and the only way to do that correct is to use the http envelope. If you wanted to use UNICODE encoding what is default for HTML4/XHTML we had to deliver our documents with 2byte characters and starting with either 0xFF 0xFE or 0xFE 0xFF. What can be done by mbstring module.

Since PHP's Content-Type header only contains 'text/html' it should be specified in a meta tag. As far as I know phpinfo() output is always in english regardless of the machine's charset settings, therefor charset should always be set to 'iso-8859-1', regardless of what the user generated pages send as their charset.

The characterset used by the executable depends on the machine used to compile it. AND everyone could use a php ini file that changes the characterset being used for output. And using iso-8859-1 chartable has nothing to with the language english only that english sites mostly use that table. As soon as they get euro currency the will switch to iso-8859-15 table that is slightly different (just as we in germany and many other european countries did). If you want to send charset you can simply exclude default_mimetype and default_charset in your php ini and use header() function to send your own appropriate content-type http info. Maybe adding charset from mbstring if active s worth a patch. I'll take a look... marcus