> I've done a nasty hack now for writing the trademark, but it works. >
Humm. It would proabably have been easier to use BiffViewer. You could have just looked at it in the SSTRecord. > where the buffer is a ByteArrayOutputStream, and I write bytes[] out in a for- > loop. After looking, comparing and so on I found out that the tm is represented > as the byte value -103. > Normally the Hex representation(as seen in ultraedit) of a trademark is a " > followed by a !. > A tm written with hssf is represented by a tm and a ".". > Here's an example from ultraedit: > > HSSF written: ...99 00... > > EXCEL normally: ...22 21... > > what caused a great deal of confusion with me was the fact that the trademark > is here written as hex 99(deci 153 which is the ascii value), and that 153 > doesn't occur in the outputstream. > Ahh this smells familiar. Did you write it as a 16 bit (unicode) string? See if that works. > Maybe I'm stupid, but this is probably because I've forgotten all of my > schooling through massive consumption of alcohol. I suppose it's because of > binary conversion: > > -103 = 01100111 (conversion)=> 10011000+1 = 10011001 = 153 > > But anyway, if I look at every single byte, and replace the value pattern 99 0 > by 22 21, the tm's in EXCEL are displayed allright. I suppose all ascii > characters between 129 and 159 will have this problem. > hehe...ASCII ends at 127 I believe :-) -- Anyhow, I think if you grab the (CVS) head and set to 16-bit mode, it will look right. Let me know if it doesn't. > If there are questions as to what the hell I'm talking about, please don't > hesitate to ask here, I'll get an e-mail about it... -Andy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
