[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[commit-cp] [bugs #9105] Wrong maxBytesPerChar from UTF-16BE, UTF-16LE a
From: |
Michael Koch |
Subject: |
[commit-cp] [bugs #9105] Wrong maxBytesPerChar from UTF-16BE, UTF-16LE and UTF-16 |
Date: |
Fri, 15 Oct 2004 05:11:59 -0400 |
User-agent: |
Mozilla/5.0 (compatible; Konqueror/3.2; Linux) (KHTML, like Gecko) |
This mail is an automated notification from the bugs tracker
of the project: classpath.
/**************************************************************************/
[bugs #9105] Latest Modifications:
Changes by:
Michael Koch <address@hidden>
'Date:
Fre 15.10.2004 at 09:04 (GMT)
What | Removed | Added
---------------------------------------------------------------------------
Resolution | None | Fixed
Status | Open | Closed
------------------ Additional Follow-up Comments ----------------------------
I just commited a fix for this. The suggested solution was correct. I commited
a testcase to mauve for this too. Thanks for your contribution.
/**************************************************************************/
[bugs #9105] Full Item Snapshot:
URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=9105>
Project: classpath
Submitted by: Tom Quarendon
On: Mit 26.05.2004 at 09:29
Category: None
Severity: 5 - Average
Resolution: Fixed
Privacy: Public
Assigned to: None
Status: Closed
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.
Follow-up Comments
------------------
-------------------------------------------------------
Date: Fre 15.10.2004 at 09:04 By: Michael Koch <mkoch>
I just commited a fix for this. The suggested solution was correct. I commited
a testcase to mauve for this too. Thanks for your contribution.
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/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [commit-cp] [bugs #9105] Wrong maxBytesPerChar from UTF-16BE, UTF-16LE and UTF-16,
Michael Koch <=