poi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew C. Oliver" <acoli...@apache.org>
Subject Re: unicode support
Date Wed, 03 Sep 2003 20:36:06 GMT
If you ruin it...the unit tests should fail.  :-)

On 9/3/03 5:27 PM, "A. Rothman" <amichai@amichais.net> wrote:

> I had performance in mind as well, but then I saw there
> 
> String unicodeString = new
> String(getString().getBytes("Unicode"),"Unicode");
> 
> which is exactly the same performancewise, only this doesn't do anything
> (since unicode conversion doesn't lose nor gain any data in the conversion -
> it just decomposes and recomposes the string). also "Unicode" appears
> neither in the JVM required encodings list or sun supported encodings...it
> may be very JVM dependent.
> 
> I'd still like to hear if anyone knows what that code section does before I
> ruin anything :-)
> 
> ----- Original Message -----
> From: "Andrew C. Oliver" <acoliver@apache.org>
> To: "POI Developers List" <poi-dev@jakarta.apache.org>
> Sent: Wednesday, September 03, 2003 10:18 PM
> Subject: Re: unicode support
> 
> 
>> We've done detection before...its always a huge performance and memory
> hog.
>> In any case, I don't think this method has been tried.  So go for it and
> see
>> what happens.
>> 
>> -Andy
>> 
>> On 9/3/03 5:18 PM, "A. Rothman" <amichai@amichais.net> wrote:
>> 
>>> Hey guys,
>>> 
>>> After experiencing some unicode trouble with HSSF today, namely setting
> the
>>> cell encoding before setting it's text (or lack thereof...), I figured
> since
>>> Java is unicode based it's not too friendly to require users to set
> unicode
>>> flags explicitly in order for unicode to work. I traced the problem down
> to
>>> UnicodeString.serialize(), and found some rather strange code that seems
> to do
>>> nothing (decomposing and creating a string, try and catch blocks that
> are
>>> identical...anyone have any ideas?), and thought we should have the
> serializer
>>> (or perhaps the constructor?) detect the case where the String contains
>>> non-ascii/iso-latin chars and set the encoding automatically. This can
> be as
>>> simple as a
>>> 
>>> if (str.equals(new String(str.getBytes("iso8859_1"),"iso8859_1"))) //
> string
>>> can be compressed
>>> ...
>>> 
>>> what do u say? any implications I didn't think of?
>>> 
>>> 
>>> -Amichai
>>> 
>> 
>> -- 
>> Andrew C. Oliver
>> http://www.superlinksoftware.com/poi.jsp
>> Custom enhancements and Commercial Implementation for Jakarta POI
>> 
>> http://jakarta.apache.org/poi
>> For Java and Excel, Got POI?
>> 
>> The views expressed in this email are those of the author and are almost
>> definitely not shared by the Apache Software Foundation, its board or its
>> general membership.  In fact they probably most definitively disagree with
>> everything espoused in the above email.
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: poi-dev-help@jakarta.apache.org
>> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: poi-dev-help@jakarta.apache.org
> 

-- 
Andrew C. Oliver
http://www.superlinksoftware.com/poi.jsp
Custom enhancements and Commercial Implementation for Jakarta POI

http://jakarta.apache.org/poi
For Java and Excel, Got POI?

The views expressed in this email are those of the author and are almost
definitely not shared by the Apache Software Foundation, its board or its
general membership.  In fact they probably most definitively disagree with
everything espoused in the above email.


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


Mime
View raw message