-
Bug
-
Resolution: Unresolved
-
P4
-
6u10, 8
-
Cause Known
-
generic, x86
-
generic, windows_xp
FULL PRODUCT VERSION :
ADDITIONAL OS VERSION INFORMATION :
all OS
A DESCRIPTION OF THE PROBLEM :
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.
see bug:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4508058
look mat the comments too.
look at the vote number.
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
Application code must recognize and skip the BOM itself.
ADDITIONAL OS VERSION INFORMATION :
all OS
A DESCRIPTION OF THE PROBLEM :
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.
see bug:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4508058
look mat the comments too.
look at the vote number.
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
Application code must recognize and skip the BOM itself.
- duplicates
-
-
- Closed
-
- relates to
-
-
- Resolved
-
-
-
- Closed
-
-
JDK-4508058 UTF-8 encoding does not recognize initial BOM
-
- Closed
-