Re: Request for an Apache configuration change

[James Henstridge <james daa com au>]

On 8/04/2004 3:12 PM, Ross Golder wrote:

> Did this ever get fixed, and if so what was the outcome?
>  
Well, the server is serving HTML as "text/html" rather than 
"text/html;charset=UTF-8" now, so the initial problem was fixed.

> I noticed on gnome-i18n a post with a list of non-UTF8 po files, that
> hopefully will get dealt with soon, which should lessen the problem :)
> Anyone not using UTF-8 should get a complimentary slap on the wrist.
>  
Sure standardising on UTF-8 is a good idea.  However the current web 
site isn't all in UTF-8.  If we agree that it is desirable for 
everything to be in UTF-8, there are two ways we can get there:

  1. Convert everything at once.  In this case, AddDefaultCharset is
     okay, since you just have to change the default after the change.
  2. Convert the content piece by piece.  In this case,
     AddDefaultCharset is harmful because it will be setting the wrong
     encoding for some percentage of documents.  It is better to leave
     the encoding out of the Content-Type and let the web browser
     detect the encoding from the content of the file.

I personally think that (1) is unrealistic.  With (2), it would be 
possible to reenable the AddDefaultCharset option after the conversion 
was complete, but it would be unnecessary.

James.

--
Email: james daa com au
WWW:   http://www.daa.com.au/~james/