Hello Maksym, On Sun, 25 Jan 2004 20:02:39 +0200 GMT (26/01/2004, 01:02 +0700 GMT), Maksym Kozub wrote:
TF>> just because it doesn't detect a high ASCII character? > Yep. Looks exactly so. TF>> That sounds wrong. > For me too. OK, let's read on: > Alexandr Kiselev, administrator, Dec 02, 2003, 07:28:24 pm: > -------------------------------------------------------------------------------- > "If all characters in a message are us-ascii, then Bat has been always > putting us-ascii in message headers, irrespective of the default > encoding. This is by the way in complete accordance with the letter > and spirit of RFCs. The others confirm that's so in the RFCs. > I would recommend to replace one of Latin "a"'s with a Russian "а" - > this would be sufficient to cope with your problem. Here you have a work-around that should solve your problem for the time being. But having read the discussion you kindly translated, I don't consider it a bug in TB. Because TB behauves RFC-conform (if what was said in the thread from the forum is true, I didn't check it). The work-around is therefore for an RFC, which I - as you - think should be altered. The correct way is to write to the author of the RFC rather than asking Ritlabs to violate it. I believe they have a right to be proud of their RFC-compliance. If an RFC doesn't make sense, it ought to be changed rather than ignored. IMHO. -- Cheers, Thomas. Moderator der deutschen The Bat! Beginner Liste. "I'm in favor of love as long as it doesn't happen when 'The Simpsons' are on TV." (Anita, 6) Message reply created with The Bat! 2.03.47 under Chinese Windows 98 4.10 Build 2222 A using a Pentium P4 1.7 GHz, 256MB RAM ________________________________________________ Current version is 2.02.3 CE | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
