A Utf-8 stream can optionally beign with a byte order mark (see, for example http://www.unicode.org.unicode/faq/utf_bom.html). This is the character FEFF, which is represented as EF BB BF in utf-8. Java's utf-8 encoding does not recognize this character as a BOM, though; the result of reading such a stream is a set of characters bginning with FEFF.
The assumption we made to implement this RFE is that the change would not
break existing real world application, this assumption is obvious not true,
see #6378911. We decided to back out the change we've made and closed this
RFE as "will not fix", for compatibility reason.
Application code must recognize and skip the BOM itself.
Recognize the BOM, just as UTF-16 does.
Java does not recognize the optional BOM which can begin a UTF-8 stream. It treats the BOM as if it were the initial character of the stream.