Hi there!
On 24 Apr 00, at 4:06, Thomas Fernandez wrote
about "UTF encoding":
> thanks for the HTML attachment in Thai, but it displayed as Chinese
> characters. I assume the reason is that there is no header in your
> message saying:
>
> Content-Type: text/plain;
> charset="utf-8"
>
> That I got from SyP and it worked. Below is your header showing
> content-type but no charset. So I guess the system assumes default.
> t> Content-Type: multipart/mixed; boundary="----------A64A10737236B24"
Thomas, you'd better have a look at the RFCs (2045 and succeeding 3) prior
to making these conclusions. The Content-type is by RFCs set for *each* part
of multipart messages (i.e. messages containing attachments of any sort)
independently, it's set not in the main message headers where from you cut
and pasted the line above, but rather in each part _sub_headers.
So in short you just looked in entirely wrong place and thus made _entirely_
wrong assumptions.
HTH (although RFC2045 would have helped much better).
--
SY, Alex
(St.Petersburg, Russia)
http://mph.phys.spbu.ru/~akiselev
---
Thought for the day:
You cannot successfully determine beforehand which side of the
bread to butter.
---
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 TBBETA archive at http://tbbeta.thebat.dutaint.com
To send a message to the list moderation team double-click HERE:
<mailto:[EMAIL PROTECTED]>
To Unsubscribe from TBBETA, double-click HERE:
<mailto:[EMAIL PROTECTED]>
--------------------------------------------------------------
You are subscribed as : [email protected]
