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;-)
Yes, you are right ;)
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.
My mozilla displays the /he2/ files improperly. Though Kokqueror uses the right encoding. If I use
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-8-I">
Mozilla and Konqueror also understands the encoding and displays the content correctly. I have checked /he/, /he1/ to /he4/ and none of the index files there used the above meta tag, so I guess this was not tried before. Though this is what the HTML standard says. Here is the list of charsets referenced in the HTML standard:
http://www.iana.org/assignments/character-sets
1) An HTTP "charset" parameter in a "Content-Type" field.
We will have this on php.net.
And I/we? were talking only about offline html not about phpweb, which could probably behave different!
Yes. php.net will have a HTTP header, the offline version should have a proper <meta>.
Goba