Bug 22957

Summary: [PATCH] Transparent use of unicode when setting cell content
Product: POI Reporter: amichai
Component: HSSFAssignee: POI Developers List <dev>
Status: RESOLVED FIXED    
Severity: normal    
Priority: P3    
Version: 3.0-dev   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Attachments: patch that automatically detects unicode strings and uses uncompressed unicode in the excel format
a unit test for UnicodeString (after fix is applied)

Description amichai 2003-09-06 10:00:14 UTC
Setting a cell's content to a String containing unicode characters loses the 
unicode content unless setEncoding() is called first explicitly. This is 
unfriendly and unintuitive to developers using HSSF, since Java applications 
are expected to run with Unicode transparently. It should not be possible to 
lose unicode content under any circumstances, since it renders the String 
meaningless in any case.
Comment 1 amichai 2003-09-06 10:01:43 UTC
Created attachment 8080 [details]
patch that automatically detects unicode strings and uses uncompressed unicode in the excel format
Comment 2 amichai 2003-09-06 10:03:45 UTC
Created attachment 8081 [details]
a unit test for UnicodeString (after fix is applied)
Comment 3 Avik Sengupta 2003-09-06 14:11:48 UTC
Thanks.. this is very nice. However, before we commit this, we need some more
feedback on this, since most of us dont us multi byte character sets. So can
some people use this patch and leave a note on this bug on their experiences. We
also need people to test it with different default encodings in their machines. 
Comment 4 Jason Height 2006-01-03 12:44:03 UTC
Due to underlying changes the patch is no longer appropriate. The good news is
that  i believe all of tghe unicode support is now in SVN.

Holler if i have missed something.

Jason