Edward H. Trager wrote:
Thanks, Pablo!
You have a good point that perhaps Apache should have no encoding set by default, thus forcing everyone to read the documentation and make a decision.
Does anyone else have an opinion on this?
I think that HTTP's "Content-Type: text/html" should automatically imply
"Content-Type: text/html; charset=UTF-8", like xml does. But since thats not the
case I configure my apache server to be explicit. (the HTTP setting seems to
override any META tags in individual pages, but I'm fine with that.)
For the most part, I think that even having a choice of encoding is a source
of problems, and it'd probably be better all around if it simply wasnt configurable,
outside of conversion programs such as iconv. I think its high time to treat
encoding as a solved problem and move on to the trickier aspects of i18n.
-- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
