-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Oscar,
On 4/2/2009 1:30 PM, Je suis la poubelle wrote: > On Fri, Mar 27, 2009 at 5:34 PM, Christopher Schultz > <ch...@christopherschultz.net> wrote: >> While it's not a terrible idea to specify the encoding in both places, >> you should consider the possibility that the META tag can be wrong. > > It's not only "not a terrible idea", but a good habit to do so. Just > like the principle of "double check": what's the point of double check if > everything works as expected? We do "double check" because in practice we > are subject to errors. The problem is when the web server sends a response, it sends it using a particular character set (let's just say UTF8 for argument's sake). If you also report that the character set is UTF8 in the META tags, then it's only valid if the client saves the file to the disk with that same character encoding. If a different encoding is being used, then the file is "lying" about its own encoding. > A good programmer should never leave anything to chance, that's why > it's good to set charset in both HTTP header as well as in HTML header. I've never used META to set the content type of a web page, and things seem to be working just fine over here. <shrug> - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAknWgYUACgkQ9CaO5/Lv0PA8XwCfQH4iBwSY/6Pl4OjTUYA14e/Y 09YAn2iaagNDRrVysIZAqzWcY6MCM2yD =MFJ5 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
