------- Comment #4 from marcus at better dot se 2008-02-03 20:43 ------- The bug is still in gcj 4.3. The Sun API docs are quite clear about how this should behave:
"When decoding, the UTF-16 charset interprets a byte-order mark to indicate the byte order of the stream but defaults to big-endian if there is no byte-order mark; when encoding, it uses big-endian byte order and writes a big-endian byte-order mark." [1] ~$ gij-4.3 --version java version "1.5.0" gij (GNU libgcj) version 4.3.0 20080116 (experimental) [trunk revision 131577] [1] http://java.sun.com/javase/6/docs/api/java/nio/charset/Charset.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28977
