From: "ST"<[EMAIL PROTECTED]>
We've supported MESSAGE with text/plain to exchange ASCII. But how
to support other encodings for other languages, like, UTF-8?
I tested eyebeam, which encodes a chinese character into
sth. neither GB2312 nor Unicode. I wonder what that encoding
is. and it uses text/html.
So what is the standard other than text/plain (rfc 2646)? Thank you.
I don't know how thoroughly the body of MESSAGE is standardized. (You
can read the RFC as well as I can, I expect.) But for consistency
with other systems, I would expect that if the body is plain text, and
it is encoded in a system other than US-ASCII, the request would
specify the encoding in the Content-Type header in the usual way:
Content-Type: text/plain; charset=utf-8
Content-Type: text/plain; charset=GB2312
See RFC 2046, section 4.1. The IANA registry for charset's is at
http://www.iana.org/assignments/media-types-parameters, but seems to
have few entries. I suspect that many more values have been used
without being registered.
Dale
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
