Re: Multiple char encodings for site internationalzation

Quoting Hironori Sato <satoh@jpnnet.com>: > So, if one wants to design a system which can accommadate all sorts of > charset, locale should be defined somewhere on the server side. The only > solution that I can think of is to define the locale for each language. An > example would be setting up virtual server like this: [snip] > may be there is nicer way to handle this, any ideas? I'm not sure, but this way of doing things would be pretty much useless for webmail - there's no way I'm going to get someone to set up 10 or 12 virtual servers just to handle different encodings, and that wouldn't work with non apache servers. There's absolutely no way to tell what charset you're going to want to handle an email in. *However*, you do always know that charset that it's in - you don't have to examine the text to find out, you read it from the headers. If the sending mail program didn't bother putting it in the headers, you assume us-ascii, and if that's wrong, well, the program that sent it is broken. I don't know if that helps any... -chuck -- Charles Hagenbuch, <chagenbu@wso.williams.edu> -- ...and remember: elmo is _not_ an insertion toy.