Bill Moseley <[email protected]> writes: > It's a server configuration error. If you are serving static files > make sure they are encoded correctly and then set AddDefaultCharset to > match. That can be done in .htaccess if you don't have access to the > server config.
Unless the server config blocked .htaccess functionality. > Anyway, I'm wondering if the template is the correct place to do what > you asking. It may not be the correct place but it is a 100% reliable approach. All other alternatives require some control over the web server, control that is not always available. If you create trees of HTML documents that need to be serviced by different servers that you have no control over you run out of luck pretty soon. >> RedHat started adding 'AddDefaultCharset UTF-8' a couple of years ago to >> the distributed server configs. Not funny. > > That seems like a reasonable default. If files are ASCII on disk then > they are fine. Except that the default until then was ISO-8859.1 and the files on disk were Latin1, not ASCII. And, as you may know. Latin1 files are not compatible with UTF8 files. >> Therefore I adapted the habit to always use &entities; for anything >> non-ASCII. > > Seems so last century. ;) It is. I may reconsider this approach if *every* server I encounter services UTF8 encoded documents. And then the only thing I need to do is remove the html_nonasc filter from page/wrapper... -- Johan _______________________________________________ templates mailing list [email protected] http://mail.template-toolkit.org/mailman/listinfo/templates
