Hello Thomas, Monday, January 26, 2004, 8:01:14 PM, you wrote:
>> The behaviour you propose cause more problems because some systems >> (especially those functioning in the US and Canada) do not know anything >> about character sets other than us-ascii (and ISO, if one is lucky) >> and that caused problem with message processing and the recipient may >> not get the message. TF> Hm. If he does use a high ASCII character, the encoding will not be TF> changed by TB. Well, here is the problem - I use a Russian character set by default. When I send messages in English, I'm always sure that they're going out in us-ascii, no need to change anything here. Now, imagine I'm sending a message in English to some of those servers from the above - in best case, I'll get my message back saying server could not process it because an unknown character set. But I used only English! :-) Do you see my point? Another point - some MUAs may/will choose different fonts for viewing messages in a non-Western character set because of font mangling... TF> What you do is change the encoding despite the sender's explicit TF> wish. Not exactly. I wish my messages I write in Russian to go out in the character set I choose. But if I write messages in English, I don't want to mess with switching my encoding - all I want is just to write a message and be sure the recipient will be able to read it without any problems :-) -- Cheers! Stefan
pgp00000.pgp
Description: PGP signature
________________________________________________ Current version is 2.02.3 CE | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
