frantisek holop writes: > > For dynamic content it's even simpler -- the program producing the > > content should also provide the corresponding header information. > > and it does so inside the <head> of the page. > a perfectly normal and accepted practice. > btw. a content-type meta tag is _mandatory_ > in most doctype's. go on, leave it out, cause it's "ugly"
Not a single doctype requires a meta content-type tag. Although it's good practice to include one for servers that don't specify a charset in HTTP, the fact is that if for any reason the server specifies a different charset, it will override the one in the meta tag. This is historical practice (and probably correct according to RFC) and will never change.
