[bugs #9105] Wrong maxBytesPerChar from UTF-16BE, UTF-16LE and UTF-16

[Tom Quarendon]

This mail is an automated notification from the bugs tracker
 of the project: classpath.




/**************************************************************************/
[bugs #9105] Full Item Snapshot:

URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=9105>
Project: classpath
Submitted by: Tom Quarendon
On: Wed 05/26/04 at 09:29

Severity:  5 - Average
Resolution:  None
Assigned to:  None
Status:  Open
Platform Version:  None


Summary:  Wrong maxBytesPerChar from UTF-16BE, UTF-16LE and UTF-16

Original Submission:  Seems like the UTF-16BE and UTF-16LE charset encoder 
classes return 4 from maxBytesPerChar because they are allowing for a byte 
ordering mark. Equally the UTF-16 charset encoder class returns 2. I think that 
the values passed to the UTF_16Encoder constructor for the useByteOrderMark 
parameter are the wrong way around.











For detailed info, follow this link:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=9105>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/