Hello SyP,
Wednesday, March 06, 2002, 1:53:43 PM, you wrote:
Many thanks for your reply and explanation. Sorry about the delay in
responding -- I have been too busy to read by batmail for a few days.
S> It's quoted-printable encoding - in other words, all bytes are changed
S> to =XX where XX is the byte's value in hex. if you see this, something
S> clearly went wrong, but I don't know if the error is on the sender or
S> on the recipient's side, if I can't see the whole MIME message.
Here is an example of the source of an entire message sent from
Outlook Express encoded in utf-8.
Return-Path: <[EMAIL PROTECTED]>
Received: from creeocxkgo42pm (ppp116-224.lino.sympatico.ca [142.217.224.116])
by hermes.lino.com (8.11.5/8.11.5) with SMTP id g2DGhDA21891
for <[EMAIL PROTECTED]>; Wed, 13 Mar 2002 11:43:13 -0500 (EST)
Message-ID: <002001c1caaf$63b94ba0$74e0d98e@creeocxkgo42pm>
From: "David Denton" <[EMAIL PROTECTED]>
To: "David Denton" <[EMAIL PROTECTED]>
Subject: syllabics
Date: Wed, 13 Mar 2002 11:51:52 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_001D_01C1CA85.775AB920"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-UIDL: ?+%"!LP@"!+FJ!!3:2!!
------=_NextPart_000_001D_01C1CA85.775AB920
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
=E1=90=A7=E1=90=8A=E1=92=8B=E1=90=A7=E1=90=8B =
=E1=91=8C=E1=90=B1=E1=91=A6 =E1=91=8C=E1=93=90=E1=91=90=E1=93=90
=E1=91=96=E1=93=90 =E1=90=81 =E1=91=8E=E1=94=A8=E1=93=90=20
------=_NextPart_000_001D_01C1CA85.775AB920
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3D"BJCree UNI" =
size=3D2>=E1=90=A7=E1=90=8A=E1=92=8B=E1=90=A7=E1=90=8B =
=E1=91=8C=E1=90=B1=E1=91=A6 =
=E1=91=8C=E1=93=90=E1=91=90=E1=93=90</FONT></DIV>
<DIV><FONT face=3D"BJCree UNI" size=3D2>=E1=91=96=E1=93=90 =E1=90=81 =
=E1=91=8E=E1=94=A8=E1=93=90 </FONT></DIV>
<DIV> </DIV></BODY></HTML>
------=_NextPart_000_001D_01C1CA85.775AB920--
S> Btw. I typed in the hex values in an editor, and loaded into UniPad, a
S> Unicode-enabled free, comprehensive editor, and they looked like
S> Canadian aboriginal symbols.
Yes, it is Cree syllabics in the United Canadian Aboriginal Syllabics
plane. I use UniPad, too. It is a great tool.
I tried experimenting with the Transport settings for the account
relating to how 8-bit characters are treated. This does not seem to
change anything. If I understand what is happening here, The Bat! seem
to convert the Unicode text to quoted-printable no matter what.
What if I had a fixed-width syllabic font, would that allow me to
view the message as text?
I did discover that if I view the html message in Internet Explorer, I
see the message correctly, which partially solves my problem. IE seems
to read the quoted-printable and to switch it to utf-8. I wonder why
TB!'s own html viewer cannot view this same text. What would it take
to get it to recognize the utf-8 encoding?
--
Best regards,
David
Using The Bat! v1.53d on Windows NT
5.0 Build 2195
Service Pack 2
--
________________________________________________________
Archives : http://tbudl.thebat.dutaint.com
Moderators : mailto:[EMAIL PROTECTED]
TBTech List: mailto:[EMAIL PROTECTED]
Unsubscribe: mailto:[EMAIL PROTECTED]
Latest Vers: 1.53d
FAQ : http://faq.thebat.dutaint.com
