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=27394>. 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=27394 A space may enter behind a character when the enclosed alphanumerics characters are read. ------- Additional Comments From [EMAIL PROTECTED] 2004-03-06 01:40 ------- The string contains 'Far East Info', which I don't think is handled properly by HSSF. Here is what the String element looks like inside the SST record (beginning at offset 0x08) 01 00 Length of String = 1 character 05 Flags Far East Info, Unicode Characters 10 00 00 00 Length of Far East Info = 16 bytes 60 24 Unicode code points = \u2460 = ① 01 00 0C 00 Far East Info (Undocumented 16 bytes) 05 00 35 00 00 00 00 00 00 00 00 00 I looked at the class org.apache.poi.hssf.record.UnicodeString, and I believe this class does not understand Far East information Strings (Option = 0x04 through 0x07). This class assumes that the first byte of the String will be at offset 3 from the beginning of the SST element. But it's not that simple. The options flag at offset 2 may indicate that the String contains 'Far East Information' (if the bit at 0x04 is set). In this case, the length of the Far East Information is at offset 3, and the first character of the string begins at offset 7. Also, the code page present in the spread sheet is 1200. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
