Hi,
I'm a bit confused with: View->Character Set in the main drop down
menu on the main window and Right Mouse Click->Encoding option on the
message window when it's opened. Will call later on first one A) and
second one B). Message is in UTF-8 ; OS is English.
What is a difference between them? Shouldn't just setting A be enough?
Now to display properly Simplified message I need NOT TO modify A (let
TB! to detect it) BUT additionally I need to set B.
However, there are following issues for Simplified Chinese:
- if A is set to autodetect Chinese Simplified messages I have are
displayed in Cyrillic (embedded graphics in messages is replaced by
Cyrillic strings as well).
- if TB! B section is set to AutoDetect almost each Simplified
Chinese (S_CHN) message is displayed improperly (A is detected as
UTF-8 - proper ; B was set by default to Western European (Windows) -
AutoDetect Option was not active).
If you turn off AutoDetect and turn it on - message is displayed
properly. When you go to other message and back to that one it's wrong
again up to the moment it's manually corrected.
For some reasons TB! first AutoDetect identifies it as GB2312 but
second AutoDetect (manual one) identifies it as UTF-8 (that is
proper).
- After message is manually re-AutoDetected and clicked twice to open,
previously selected encoding is reset to GB2312 despite that it was
just properly re-AutoDetected. After re-AutoDetected again it's good
again.
- After above properly re-AutoDetected message is reply message is
coded in UTF-8 but probably Chinese characters were again enforced to
GB2312 and that makes all Chinese part unreadable while Reply to.
----
TRADITIONAL CHINESE
I was not able to properly display a message coded in GBK. Some
characters were replaced by question marks.
For some reasons TB! detected it as UTF-8 while it's coded in GBK.
--Apple-Mail-71-707530316
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=GBK
Reply to such message scrambles all message as it was detected as
UTF-8 and TB! codes it in UTF-8 while it's in GBK.
----
POLISH LANGUAGE
Newsletter send from Allegro.pl is coded in UTF-8 but detected as
Central European (Windows).
Subject: =?UTF-8?Q?Nowe_oferty_27-04-2012?=
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-type: text/html; charset=UTF-8
From: Allegro <[email protected]>
Reply-To: Allegro <[email protected]>
Another newsletter first was detected as Central European (ISO) and
then as Central European (Windows):
From: Plastics Online Newsletter <[email protected]>
Subject: Polimerowa Energia
X-Priority: 3
X-Mailer: PHPMailer (phpmailer.sourceforge.net) [version 2.0.4]
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/html; charset="utf-8"
--
Best Regards,
RS (FEDARA)
The Bat! 5.1.2
Windows 7 x64 Professional (7601 Service Pack 1)
Friday, April 27, 2012 (11:36 ; GMT+8)
________________________________________________________
Current beta is 5.1.0.3 | 'Using TBBETA' information:
http://www.silverstones.com/thebat/TBUDLInfo.html
