Re: cvs: phpdoc / Makefile.in

From: Date: Mon, 19 May 2003 09:11:08 +0000
Subject: Re: cvs: phpdoc / Makefile.in
References: 1 2  Groups: php.doc 
Request: Send a blank email to phpdoc+get-969353642@lists.php.net to get a copy of this message
On Mon, 19 May 2003, Gabor Hojtsy wrote: > > no, that doesn't work too. look, the only way to tell the browser to use a > > specific encoding (that goes for most popular browsers) is: > > <meta charset="encoding">. No content=text/html, not http-equiv, and not > > anything that differs from <meta charset="encoding">. That's how it > > is, > > and that's a given fact in MSIE and Mozilla, which together hold more than > > 99% of the world browsers... > > Khm.... Can you please show me, what standard specifies this <meta > charset=""> format? I am unable to find this in HTML 4.01: > > http://www.w3.org/TR/html4/struct/global.html#h-7.4.4.2 > > As other encodings work with <meta http-equiv="Content-type" > content="text/html; encoding=..."> it is very hard to beleive me, that > only a non-standard way works for Hebrew. Please note that we are not > going to add any non-standard markup to the PHP site. We need to find > out, how will this work with standards. It should. All <meta>'s are allowed AFAIK: The META element can be used to identify properties of a document (e.g., author, expiration date, a list of key words, etc.) and assign values to those properties. This specification does not define a normative set of properties. so it's fine to add the charset="" thingy (which Mozilla definitely requires) Derick -- "my other box is your windows PC" ------------------------------------------------------------------------- Derick Rethans http://derickrethans.nl/ International PHP Magazine http://php-mag.net/ -------------------------------------------------------------------------

« previous php.doc (#969353642) next »