The same character converted to UTF-8 becomes the byte sequence EF BB BF. The Unicode Standard allows that the BOM "can serve as signature for UTF-8 encoded text where the character set is unmarked". Some software developers have adopted it for other encodings, including UTF-8, in an attempt to distinguish UTF-8 from local 8-bit code pages. However RFC 3629, the UTF-8 standard, recommends that byte order marks be forbidden in protocols using UTF-8, but discusses the cases where this may not be possible. In addition, the large restriction on possible patterns in UTF-8 (for instance there cannot be any lone bytes with the high bit set) means that it should be possible to distinguish UTF-8 from other character encodings without relying on the BOM.
The same character converted to UTF-8 becomes the byte sequence EF BB BF . The Unicode Standard allows that the BOM " can serve as signature for UTF-8 encoded text where the character set is unmarked " . Some software developers have adopted it for other encodings , including UTF-8 , in an attempt to distinguish UTF-8 from local 8-bit code pages . However RFC 3629 , the UTF-8 standard , recommends that byte order marks be forbidden in protocols using UTF-8 , but discusses the cases where this may not be possible . In addition , the large restriction on possible patterns in UTF-8 ( for instance there can not be any lone bytes with the high bit set ) means that it should be possible to distinguish UTF-8 from other character encodings without relying on the BOM .
Why is it possible to distinguish UTF-8 from other protocols?
Why is it possible to distinguish UTF-8 from other protocols ?
the large restriction on possible patterns
the large restriction on possible patterns