DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11322>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11322 can't read ������ ... sometimes. Summary: can't read ������ ... sometimes. Product: POI Version: 1.5.1 Platform: Sun OS/Version: Other Status: NEW Severity: Major Priority: Other Component: HSSF AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Excel saves these values differently depending on which other characters are in the cell, which means if it only says(CASE 1): ������ and you try to read the cell: HSSFCell cell = (HSSFCell)cellI.next(); if(cell.getCellType() == HSSFCell.CELL_TYPE_STRING ) { cell_value = cell.getStringCellValue(); } Then the resulting String is comprised of chars, all with the integer value 65533. On the other hand, if you write other characters into the cell(CASE 2), sometimes they are read correctly. This is because normally the chars(as read in hexidecimal values) are seperated by 00(CASE 2) chars, but somtimes not. And when they are not(CASE 1), the usermodel and eventmodel can't read them. I hope I missed out on something about character sets or what do I know, if not, this is a nasty bug. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
