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. ------- Additional Comments From [EMAIL PROTECTED] 2002-08-29 13:54 ------- What I've narrowed it down to, is that in the SSTDeserializer, when you call processString, and say: UnicodeString string = new UnicodeString(UnicodeString.sid, (short) unicodeStringBuffer.length, unicodeStringBuffer ); String chars = string.getString(); for( int i = 0; i < chars.length(); i++ ) { System.out.print((int)chars.charAt(i) + " "); }chars = null; then if it is a there are chars between 160-255(keep in mind the bytes actually have the int value -1 & -64), then they all get converted to the value 65533 I don't know exactly where the conversion takes place, and I don't have time to look any further today, but if you know, please tell me. I'd like to solve this bug. Tomorrow I'll have a good look at the UnicodeString class. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
