Re: RFC, 5-6 octets sequence in UTF8, non short form in UTF8

Yung-Fong Tang wrote: > I read the RFC 2279 again ( > http://www.cis.ohio-state.edu/cs/Services/rfc/rfc-text/rfc2279.txt ) > 1. I cannot find any text in it mentioned about. non short form is > invalid UTF8, and First, we've already established that a revision to RFC 2279 is in the works. That

Re: RFC, 5-6 octets sequence in UTF8, non short form in UTF8

Frank, http://www.ietf.org/internet-drafts/draft-yergeau-rfc2279bis-03.txt addresses these, and version -04 of this draft will be public shortly. markus

RFC, 5-6 octets sequence in UTF8, non short form in UTF8

I read the RFC 2279 again ( http://www.cis.ohio-state.edu/cs/Services/rfc/rfc-text/rfc2279.txt ) 1. I cannot find any text in it mentioned about. non short form is invalid UTF8, and 2. It mentioned about 1-6 octets of UTF8 3. It mentioned about how to encode surrogate pair to UTF-8. But it does