[imp] 2.2.4-cvs forces charset encoding in HTTP headers

[Rich Lafferty]

On Mon, Oct 30, 2000 at 08:49:56AM +0700, Alain Fauconnet (alain@cscoms.net) wrote:
> Hello,
> 
> We have switched from a 2.2.0-pre13 version with security fixes hacked
> in, to the real 2.2.4-cvs on last Friday.
> 
> I've immediately got complaints saying that people here were unable to
> view messages with Thai characters.  The  problem  is  that  2.2.4-cvs
> sends a "charset=ISO-8859-1" in the HTTP headers  when  configured  to
> use US English. This make Thai  characters  appear  as  west  European
> accented characters.

Well, since Thai isn't English :-), there'd be no way for it to get it
right in the first place (since a browser won't know how to display
mixed Thai and US English). If I'm mistaken and one *can* display the
ASCII character set in the Thai locale, just create a fake Thai locale
with the English localization data but with the correct character set.
 
> Could we have something like a "Generic" locale setting that  uses  US
> English messages but does not force any charset  encoding ? 

No, because then the browser decides what locale to use, which is even
more unreliable. In particular, if you get it to work on a Windows
machine, then it won't work on a Mac, and vice versa. That's why that
change (outputting explicit charset headers) was made.

  -Rich

-- 
------------------------------ Rich Lafferty ---------------------------
 Sysadmin/Programmer, Instructional and Information Technology Services
   Concordia University, Montreal, QC                 (514) 848-7625
------------------------- rich@alcor.concordia.ca ----------------------