In article <[EMAIL PROTECTED]>, Brian Heinrich wrote: > > Nor do I. Then again, I fail to see the point of /not/ including > ><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">. > > Ever try to get a page to validate properly w/o defining a charset > attribute?
Please don't do that. Aside from the intrinsic ugliness of <meta http-equiv="">, that's liable to cause problems if some bright spark tries converting the page to XHTML down the road. Get the server to send a proper charset header instead, even if it means twisting the sysadmin's arm. ObDocumentation: Docbook 4.2 released. -- Chris Hoess
