Hi there!
On 16 Oct 99, at 9:53, Keith Russell wrote
about "Re: Fwd: FW: ���H: �j�Ƥj�f�r":
> > The mailer (not mentioned in these headers) is Outlook running under
> > C-Win98. Delivery of this message was via our company LAN, not via the
> > Internet.
>
> > Note how the name of the encoding system (big5) is in the Subject
> > line.
This is due to RFCs. Look yourself. The Subject line (when not
in plain ASCII) *must* be encoded to either QP (q-type) or
Base64 (b-type), and the encoding used must be specified
there. Upon receiving, the e-mail reader automatically decodes
it and never shows you the "garbage" it actually is. BTW, TB
always encodes the subject field to B-type (base64), although
RFCs say that this has to happen only in the case when the
*major* part of the Subject: field is non-ASCII... Once more,
look through RFC2047 for the details. It's in plain English:-)
Hence it must be much clearer for you then my own writings:-))
> Yes... This is interesting. As expected, the subject line in the
> message you sent me is garbage until I run UnionWay AsianSuite and set
> it to Big 5; the subject then becomes good, readable Chinese.
>
> However, if I then "Show Kludges", the subject is identified as
> ISO-8859-1, in contrast to the subject header below, which correctly
> identifies it as Big 5.
It in fact doesn't matter. Two cases:
1. with ISO-8859-1 it supposedly works this way:
a. Some text in Double-byte language (DBL from now on);
b. Each byte is encoded to ISO-8859-1;
c. The header states "ISO-8859-1";
d. On the receipient's end *his* e-mail reader needn't even to
know that this was in DBL; it just decodes it *from* ISO-8859-1
byte-by-byte... Of course, the sequence of bytes is okay now,
equivalent to what was on the sender's end;
e. Now provided that the system supports DBL (fonts etc.) it just
"glues" each pair of bytes together and displays it OK.
2. with Big5 (or any other double-byte encoding) it works as it
should, look through RFCs (again, RFCs 2045--2048).
So well, now, having wrote all this, I cannot tell you for sure
how it works in the case of TB. What I *do* know is that the
guys using Pegasus with Chineeze use ISO-8859-1 without
any problems (as far as I understood them). Simply Pegasus
doesn't support Big5 or any other bouble-byte encoding
directly.
And another thing: I cannot understand, where [the hell] TB
leads to errors? What happens if you specify ISO-8859-1 as
the default encoding, then modify the X-LAT for ISO-8859-1 to
use the proper font and script? Now if you try to send the
message in DBL to yourself, can you read it? Can somebody
else read it? And why?
> > Subject: =?big5?B?Rlc6IMLgsUg6IKRqrfSkaq9mrHI=?=
Once again, it's just a properly formed MIME Subject line... In
Base64 encoding.
SY, Alex
(St.Petersburg, Russia)
--
Thought for the day:
The more you run over a dead cat, the flatter it gets.
---
PGP public keys on keyservers:
0xA2194BF9 (RSA); 0x214135A2 (DH/DSS)
fingerprints:
F222 4AEF EC9F 5FA6 7515 910A 2429 9CB1 (RSA)
A677 81C9 48CF 16D1 B589 9D33 E7D5 675F 2141 35A2 (DH/DSS)
---
--
--------------------------------------------------------------
View the TBUDL archive at http://tbudl.thebat.dutaint.com
To send a message to the list moderation team click here:
<mailto:[EMAIL PROTECTED]>
To Unsubscribe from TBUDL, click below and send the generated message.
<mailto:[EMAIL PROTECTED]>
--------------------------------------------------------------
