https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28977
Andrew John Hughes changed:
What|Removed |Added
CC||gnu_andrew at member dot
fsf.org
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28977
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
--- 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-endia
--- Comment #3 from pinskia at gcc dot gnu dot org 2006-09-07 18:40 ---
(In reply to comment #2)
> Well, I have a library for XML processing that comes with a test suite, and it
> expects the Sun behaviour. Besides it's documented in Sun's API, so it can
> potentially matter.
Really if
--- Comment #2 from marcus at better dot se 2006-09-07 18:37 ---
(In reply to comment #1)
> Does this really matter as UTF-16 BOM is correct?
Well, I have a library for XML processing that comes with a test suite, and it
expects the Sun behaviour. Besides it's documented in Sun's API, s
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-09-07 18:28 ---
Does this really matter as UTF-16 BOM is correct?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28977
