Re: cvs: phpdoc / Makefile.in

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: > > <DEFANGED_meta charset="encoding">. No content=text/html, not http-equiv, > > and not > > anything that differs from <DEFANGED_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 <DEFANGED_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 <DEFANGED_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. > > Goba > I think that This isn't related to hebrew. Browsers don't follow "the standard" for any charset if I am not wrong. Meaning, if the page i am currently viewing has the windows-1255 charset set, and I'll click on a link to google, and google would have the "standard" meta tag, the browser will stay on windows-1255, simply because <meta charset="X"> is the format that browsers follow. (I don't know why. Perhaps it was introduced in IE and everyone used it, so that's why they follow it? Much like <marquee> which is not in the standard). Anyways, "my" way works fine in Mozilla *and* IE. All the other ways does not... Standard or not-standard, if a tag is being ignored by 99% of the browsers, I don't see a use to put it... waste of space/traffic... -- Best regards, Shimi ---- "Outlook is a massive flaming horrid blatant security violation, which also happens to be a mail reader." "Sure UNIX is user friendly; it's just picky about who its friends are."