On Wed, 22 Oct 2008, Christian Gosch wrote:
Thus maybe the HSSFRichString(String) constructor may have a little flaw on deciding whether to handle a given String as UTF16 or not: It should decide not only on the binary numeric value ( > 255 or not) but rely on Java to check if it is part of a reasonable 8bit charset. This is because there are different 8bit charsets which have "holes" with a "meaning" in other widespread charsets and vice versa.
Any chance you could write a little test case that shows this, and upload it to bugzilla? Something that creates a new workbook, and populates some high bit characters into it would be great. We can then use that to test possible fixes against
Nick --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
