I'm not really well versed in this, but I have spent some time trying to make MSIE behave with various headers.

When a user writes a file via their browser through a perl program like the webmail, the characters are converted to the default set of the program/OS that it's running on. It would not carry the browser settings into the message. It would be ISO/ASCII or whatever.

When a user goes to pick up the message, the server will send a header to tell the browser what language/char set it's using, and the browser will respond as configured (or with MSIE it will go to try to find the character set if it doesn't have it).

If you plan on sending messages in multiple languages, you will probably need to modify the program (maybe even the server settings) to respond to the browser request and the language that the browser is working in. This is probably stored in an %ENV variable somewhere.. (Again, I'd have to look it up).

But, the answer (or point) I'm trying to make is that the language the user enters the text in is determined by the browser, how the server sees it is determined by the server settings, and how the person who reads it sees it is determined by the server settings going in, coming out, and their browser settings.

Maybe this explanation helps Alex see what you are probably asking, and whether he has the answer.

It's one thing to configure a site for a different language. It's another to configure it to RESPOND IN DIFFERENT LANGUAGES altogether.