DO NOT REPLY [Bug 27394] - If the special characters (①, ②, etc.) of WINDOWS are taken, a space may enter behind a character.

[bu...@apache.org]

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

If the special characters (①, ②, etc.) of WINDOWS are taken, a space may enter behind a character.





------- Additional Comments From zalewski@optonline.net  2004-03-05 04:36 -------
I am not sure which characters are being reported as broken. But I have noticed 
a similar problem:

1.  Using Excel, set a sheet name with one of the non-ISO 8859-1 characters in 
Windows ANSII Code Page 1252. For example, this includes s caron and z caron 
(but not a caron). Caron is the little cap diacritic drawn above the character. 
Don't use any non CP 1252 characters.

2. Try to read the sheet name from POI. The character will show as a little 
square (because it is an invalid code point).

3. If you use Biff Viewer, you will see that the sheet name has been stored by 
Excel as a compressed 8 bit string.

4. If you look at the string that HSSF returns for the sheet name, you will see 
that, for example, lower case z caron is converted by HSSF into \u009e, which 
is actually not a valid code point. The proper representation of z caron is 
\u0173.

When I read the original report, I cannot tell which 'special characters' are 
being used. (They appear as little boxes in my browser). I suspect that 
the 'special characters' may be those in ASCII range 0x80 - 0x9f, which cannot 
be translated to Unicode simply by assuming that the high order byte is zero.

Also a question for sasaki: He should report what his windows code page is (if 
it is not 1252). Attaching a sample spreadsheet would probably help.

Did I even get this right? The problem is that a special character is entered 
inside a cell, with Excel. When HSSF reads the value of that cell, it displays 
the character as a little box, or possibly a space.

---------------------------------------------------------------------
To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: poi-dev-help@jakarta.apache.org