No problem. Well, I'd say the bulk of the Excel install base is in the US, UK, AU, Canada. These countries do *not* need 16 bit characters. It can significantly reduce the memory required to generate the spreadsheet and/or the transmission length (size) of the XLS file if all strings are "compressed unicode" aka 8-bit. (if you have a lot of strings). The second rationale is: this is what Excel does unless you're using a language that requires unicode.
-Andy ������ ������� wrote: >Hello! > >Sorry for disturbing and thank you for helping. :) >The problem with Sheet strings (SST) was solved with setCellEncoding(). > >I have some kind of global question: what the purpose of using not Unicode >strings. >What do you think about the idea of making all the Excel String entries >Unicode? As I see, it may solve languages problem. > >Sincerely yours, Sergei Kozello. > > >----- Original Message ----- >From: "Glen Stampoultzis" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Friday, July 05, 2002 9:25 AM >Subject: Re: International (Russian) support for HSSF/HSSF Serializer (XLS) > > > > >>I'll change it back then... To be honest it makes me nervous. I accept >>that it's not documented and it would help if it were but I'm sure more >>people will be caught by this one. I'd lean towards adding a required >>boolean parameter to setCellValue() personally as it becomes immediately >>obvious what's going on. It would break backward compatibility but I >>believe it would be preferable. >> >>I'll back out the change to the default for the moment. >> >>Regards, >> >>Glen Stampoultzis (TriNexus Pty Ltd) >>Fixed:+61 3 9753-6850 Mob:+61 (0)402 835 458 >>ICQ: 62722370 EMail: [EMAIL PROTECTED] >>URL's: http://jakarta.apache.org/poi, http://www.krysalis.org >> >> > > > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
