When using blat version after 3.2.10 to send the unicode email with unicode subject, email with garbled subject text will be received in the inbox. Can anyone look at this, please? Thanks!
Command line for testing: blat.exe c:\chn.txt -charset UTF-8 -log c:\tonyemail.log -timestamp -q -debug -server mailserver -port 25 -f "sender@sender.com" -t "receiver@receiver.com" -s "测试一下中文字体和拉丁文"
Please try this Blat executable that I posted to bug #62.
https://sourceforge.net/p/blat/bugs/_discuss/thread/da8a4bbb/8469/attachment/blat.exe
I believe this new version will fix your issue. I tested your command line here with this version and it worked for me.
Hi Chip,
Thanks for your help. I just tested by using the same file. The subject line is showing the unicode character correctly. However, the unicode email body is getting garbled. If I used the previous version of blat (3.2.10), the subject line will become garbled but the unicode email body was showing correctly. Any idea on that? Thanks.
Thank you for that update. If possible, please attach your message body text file so that I may find and fix the problem.
I went to a Supermicro.com webpage to get some Chinese text, then saved this as a Unicode text file. I also copied your subject text from above, and save that as a Unicode text file. I was able to send both and the test message looked correct. If I can get your message body file, I think this will help. You can send it directly to me at chip.programmer@att.net. If you have a picture showing what the text should look like, this will also help me.
Chip
Last edit: Chip 2015-11-30
Hi Chip,
I just sent you the sample file and screenshot. Hope it was helpful for your troubleshooting. Looks like there was BOM missing?
Thanks.
Tony
Tony,
Thank you for the email with your attachments, I was able to find and fix the problem. What I found is that Unicode does have characters in the range from 0xE000 to 0xFFFD, and I was flagging these values as not valid when converting UTF-8 to Unicode. UTF-8 allows for a sequence of 8-bit bytes to be combined to form Unicode 16-bit and 32-bit values. Since many programs and communications protocols are not Unicode aware, including Internet Protocol (IP), UTF-8 allows for programs to convert Unicode to UTF-8 and back. Blat was reading your UTF-8 formatted file and trying to convert back to Unicode for internal processing, and stopped when it found what I believed was invalid characters. This problem has been fixed and you should have already received a test message from Blat with your chn1.txt file as the message body. I hope that it shows correctly for you.
Chip
Thanks Chip. The email you sent to me does correctly show the Unicode text. When using your attached blat.ext for testing in my local machine. Looks like it is still not working. I sent the email to you via the new blat.exe.
Regards,
Tony