< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index  

Re: [Msrp] UTF-8 [14] transformation


MSRP Uses Binary Content Transfer encoding and hence there is no need to do any encodings on the data being sent. UTF8 text indicates which are the characters that can be sent using msrp. This includes alphabets form a-z, A_Z, numbers form 0-9 and other special characters. In the MSRP RFC refer
utf8text = *(HTAB / %x20-7E / UTF8-NONASCII)

   UTF8-NONASCII = %xC0-DF 1UTF8-CONT
                 / %xE0-EF 2UTF8-CONT
                 / %xF0-F7 3UTF8-CONT
                 / %xF8-Fb 4UTF8-CONT
                 / %xFC-FD 5UTF8-CONT
which says the characters supported.


On Tue, 14 Feb 2006 14:03:46 +0530, Annada Prasana <annada@xxxxxxxxxxxxxxx> wrote:

Hi All,
MSRP is a text protocol that uses the UTF-8 [14] transformation format .Is
any RFC followed to get this encoding?How MSRP uses this trans. Format?

Thanks
Annada P.
_______________________________________________
msrp mailing list
msrp@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/msrp



--
Best Regards,
Sudha V.S
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely 
for the use of the addressee(s). If you are not the intended recipient, please 
notify the sender by e-mail and delete the original message.Global Edge 
Software Ltd has taken every reasonable precaution to minimize this risk, but 
is not liable for any damage you may sustain as a result of any virus in this 
e-mail. You should carry out your own virus checks before opening the e-mail or 
attachment. Global Edge Software Ltd reserves the right to monitor and review 
the content of all messages sent to or from this e-mail address