Re: cvs: phpdoc / Makefile.in

On Monday 19 May 2003 11:20, Gabor Hojtsy wrote: > >>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 AFAIK this should read <meta http-equiv="Content-type" content="text/html; charset=..."> http://www.w3.org/TR/html4/charset.html#h-5.2.2 I wasn't able to find "content="text/html; encoding=..." in the standard;-) [...] From http://www.w3.org/TR/html4/conform.html#h-4.3 <qoute> The content type for HTML documents is defined as follows: Content type name: text Content subtype name: html Required parameters: none Optional parameters: charset Encoding considerations: any encoding is allowed Security considerations: See the notes on security </qoute> > > so it's fine to add the charset="" thingy (which Mozilla definitely > > requires) That was always there. :-) The question was _only_ if browsers could detect the he encoding automatically. Nothing else nothing more. www.holliwell.de/he2/ was produced <with meta http-equiv="Content-Type" content="text/html; charset=windows-1255">, the same way all offline html manuals form php.net specify the encoding. charset could be used , but only withContent-Type and not standalone as shimi suggested (see above). The docs at w3 we talk about use that : <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> and even all offline html docs form php.net use this the same way. [...] About user agents: http://www.w3.org/TR/html4/charset.html#h-5.2.2 <qoute> 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. </qoute> So things for he should follow the standard:-) And I/we? were talking only about offline html not about phpweb, which could probably behave different! Friedhelm